Consistent interface for opportunity

ABSTRACT

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an opportunity business object.

CROSS-REFERENCE TO RELATED APPLICATIONS

Some details of the subject matter of this specification are describedin previously-filed U.S. patent application Ser. No. 11/803,178,entitled “Consistent Set of Interfaces Derived From a Business ObjectModel”, filed on May 11, 2007, which is hereby incorporated byreference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The subject matter described herein relates generally to the generationand use of consistent interfaces (or services) derived from a businessobject model. More particularly, the present disclosure relates to thegeneration and use of consistent interfaces or services that aresuitable for use across industries, across businesses, and acrossdifferent departments within a business.

BACKGROUND

Transactions are common among businesses and between businessdepartments within a particular business. During any given transaction,these business entities exchange information. For example, during asales transaction, numerous business entities may be involved, such as asales entity that sells merchandise to a customer, a financialinstitution that handles the financial transaction, and a warehouse thatsends the merchandise to the customer. The end-to-end businesstransaction may require a significant amount of information to beexchanged between the various business entities involved. For example,the customer may send a request for the merchandise as well as some formof payment authorization for the merchandise to the sales entity, andthe sales entity may send the financial institution a request for atransfer of funds from the customer's account to the sales entity'saccount.

Exchanging information between different business entities is not asimple task. This is particularly true because the information used bydifferent business entities is usually tightly tied to the businessentity itself. Each business entity may have its own program forhandling its part of the transaction. These programs differ from eachother because they typically are created for different purposes andbecause each business entity may use semantics that differ from theother business entities. For example, one program may relate toaccounting, another program may relate to manufacturing, and a thirdprogram may relate to inventory control. Similarly, one program mayidentify merchandise using the name of the product while another programmay identify the same merchandise using its model number. Further, onebusiness entity may use U.S. dollars to represent its currency whileanother business entity may use Japanese Yen. A simple difference informatting, e.g., the use of upper-case lettering rather than lower-caseor title-case, makes the exchange of information between businesses adifficult task. Unless the individual businesses agree upon particularsemantics, human interaction typically is required to facilitatetransactions between these businesses. Because these “heterogeneous”programs are used by different companies or by different business areaswithin a given company, a need exists for a consistent way to exchangeinformation and perform a business transaction between the differentbusiness entities.

Currently, many standards exist that offer a variety of interfaces usedto exchange business information. Most of these interfaces, however,apply to only one specific industry and are not consistent between thedifferent standards. Moreover, a number of these interfaces are notconsistent within an individual standard.

SUMMARY

In a first aspect, a computer-readable medium includes program code forproviding a message-based interface for exchanging opportunity data. Themedium comprises program code for receiving, via a message-basedinterface exposing at least one service as defined in a service registryand from a heterogeneous application executing in an environment ofcomputer systems providing message-based services, a first message forrequesting replication of opportunity data, including businesstransaction information and identification of parties involved in aprospective business transaction. The first message includes a messagepackage hierarchically organized as an opportunity replication requestmessage entity and an opportunity package including an opportunityentity. The opportunity entity includes an identifier, a processing typecode and a process status valid since date. The opportunity entityincludes a status entity from a status package. The medium furthercomprises program code for sending a second message to the heterogeneousapplication responsive to the first message.

Implementations can include the following. The opportunity entityfurther includes at least one of the following: a prospect party entityfrom a prospect party package, at least one competitor party entity froma competitor party package, at least one sales employee party entityfrom a sales employee party package, an employee responsible entity froman employee responsible party, a sales unit party entity from a salesunit party package, at least one party entity from a party package, asales cycle entity from a sales cycle package, a sales forecast entityfrom a sales forecast package, a sales and service business area entityfrom a sales and service business area package, at least one businesstransaction document reference entity from a business transactiondocument reference package, an attachment folder entity from anattachment folder package, a text collection entity from a textcollection package, and at least one item entity from an item package.The opportunity entity further includes at least one of the following:system administrative data, a name, a priority code, a group code, anorigin type code, a result reason code, and a change ordinal numbervalue.

In another aspect, a distributed system operates in a landscape ofcomputer systems providing message-based services defined in a serviceregistry. The system comprises a graphical user interface comprisingcomputer readable instructions, embedded on tangible media, forrequesting replication of opportunity data, including businesstransaction information and identification of parties involved in aprospective business transaction, the instructions using a request. Thesystem further comprises a first memory storing a user interfacecontroller for processing the request and involving a message includinga message package hierarchically organized as an opportunity replicationrequest message entity and an opportunity package including anopportunity entity. The opportunity entity includes an identifier, aprocessing type code and a process status valid since date. Theopportunity entity includes a status entity from a status package. Thesystem further comprises a second memory, remote from the graphical userinterface, storing a plurality of service interfaces, wherein one of theservice interfaces is operable to process the message via the serviceinterface.

Implementations can include the following. The first memory is remotefrom the graphical user interface. The first memory is remote from thesecond memory.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a flow diagram of the overall steps performed by methodsand systems consistent with the subject matter described herein.

FIG. 2 depicts a business document flow for an invoice request inaccordance with methods and systems consistent with the subject matterdescribed herein.

FIGS. 3A-B illustrate example environments implementing thetransmission, receipt, and processing of data between heterogeneousapplications in accordance with certain embodiments included in thepresent disclosure.

FIG. 4 illustrates an example application implementing certaintechniques and components in accordance with one embodiment of thesystem of FIG. 1.

FIG. 5A depicts an example development environment in accordance withone embodiment of FIG. 1.

FIG. 5B depicts a simplified process for mapping a model representationto a runtime representation using the example development environment ofFIG. 5A or some other development environment.

FIG. 6 depicts message categories in accordance with methods and systemsconsistent with the subject matter described herein.

FIG. 7 depicts an example of a package in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 8 depicts another example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 9 depicts a third example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 10 depicts a fourth example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 11 depicts the representation of a package in the XML schema inaccordance with methods and systems consistent with the subject matterdescribed herein.

FIG. 12 depicts a graphical representation of cardinalities between twoentities in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 13 depicts an example of a composition in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 14 depicts an example of a hierarchical relationship in accordancewith methods and systems consistent with the subject matter describedherein.

FIG. 15 depicts an example of an aggregating relationship in accordancewith methods and systems consistent with the subject matter describedherein.

FIG. 16 depicts an example of an association in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 17 depicts an example of a specialization in accordance withmethods and systems consistent with the subject matter described herein.

FIG. 18 depicts the categories of specializations in accordance withmethods and systems consistent with the subject matter described herein.

FIG. 19 depicts an example of a hierarchy in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 20 depicts a graphical representation of a hierarchy in accordancewith methods and systems consistent with the subject matter describedherein.

FIGS. 21A-B depict a flow diagram of the steps performed to create abusiness object model in accordance with methods and systems consistentwith the subject matter described herein.

FIGS. 22A-F depict a flow diagram of the steps performed to generate aninterface from the business object model in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 23 depicts an example illustrating the transmittal of a businessdocument in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 24 depicts an interface proxy in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 25 depicts an example illustrating the transmittal of a messageusing proxies in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 26A depicts components of a message in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 26B depicts IDs used in a message in accordance with methods andsystems consistent with the subject matter described herein.

FIGS. 27A-E depict a hierarchization process in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 28 illustrates an example method for service enabling in accordancewith one embodiment of the present disclosure.

FIG. 29 is a graphical illustration of an example business object andassociated components as may be used in the enterprise serviceinfrastructure system of the present disclosure.

FIG. 30 illustrates an example method for managing a process agentframework in accordance with one embodiment of the present disclosure.

FIG. 31 illustrates an example method for status and action managementin accordance with one embodiment of the present disclosure.

FIGS. 32-1 through 32-3 depict an example OpportunityReplicationRequestmessage data type.

FIG. 33 depicts an example OpportunityReplicationConfirmation messagedata type.

FIGS. 34-1 through 34-19 depict an example OpportunityReplicationRequestelement structure.

FIGS. 35-1 through 35-2 depict an exampleOpportunityReplicationConfirmation element structure.

DETAILED DESCRIPTION A. Overview

Methods and systems consistent with the subject matter described hereinfacilitate e-commerce by providing consistent interfaces that aresuitable for use across industries, across businesses, and acrossdifferent departments within a business during a business transaction.To generate consistent interfaces, methods and systems consistent withthe subject matter described herein utilize a business object model,which reflects the data that will be used during a given businesstransaction. An example of a business transaction is the exchange ofpurchase orders and order confirmations between a buyer and a seller.The business object model is generated in a hierarchical manner toensure that the same type of data is represented the same way throughoutthe business object model. This ensures the consistency of theinformation in the business object model. Consistency is also reflectedin the semantic meaning of the various structural elements. That is,each structural element has a consistent business meaning. For example,the location entity, regardless of in which package it is located,refers to a location.

From this business object model, various interfaces are derived toaccomplish the functionality of the business transaction. Interfacesprovide an entry point for components to access the functionality of anapplication. For example, the interface for a Purchase Order Requestprovides an entry point for components to access the functionality of aPurchase Order, in particular, to transmit and/or receive a PurchaseOrder Request. One skilled in the art will recognize that each of theseinterfaces may be provided, sold, distributed, utilized, or marketed asa separate product or as a major component of a separate product.Alternatively, a group of related interfaces may be provided, sold,distributed, utilized, or marketed as a product or as a major componentof a separate product. Because the interfaces are generated from thebusiness object model, the information in the interfaces is consistent,and the interfaces are consistent among the business entities. Suchconsistency facilitates heterogeneous business entities in cooperatingto accomplish the business transaction.

Generally, the business object is a representation of a type of auniquely identifiable business entity (an object instance) described bya structural model. In the architecture, processes may typically operateon business objects. Business objects represent a specific view on somewell-defined business content. In other words, business objectsrepresent content, which a typical business user would expect andunderstand with little explanation. Business objects are furthercategorized as business process objects and master data objects. Amaster data object is an object that encapsulates master data (i.e.,data that is valid for a period of time). A business process object,which is the kind of business object generally found in a processcomponent, is an object that encapsulates transactional data (i.e., datathat is valid for a point in time). The term business object will beused generically to refer to a business process object and a master dataobject, unless the context requires otherwise. Properly implemented,business objects are implemented free of redundancies.

The architectural elements also include the process component. Theprocess component is a software package that realizes a business processand generally exposes its functionality as services. The functionalitycontains business transactions. In general, the process componentcontains one or more semantically related business objects. Often, aparticular business object belongs to no more than one processcomponent. Interactions between process component pairs involving theirrespective business objects, process agents, operations, interfaces, andmessages are described as process component interactions, whichgenerally determine the interactions of a pair of process componentsacross a deployment unit boundary. Interactions between processcomponents within a deployment unit are typically not constrained by thearchitectural design and can be implemented in any convenient fashion.Process components may be modular and context-independent. In otherwords, process components may not be specific to any particularapplication and as such, may be reusable. In some implementations, theprocess component is the smallest (most granular) element of reuse inthe architecture. An external process component is generally used torepresent the external system in describing interactions with theexternal system; however, this should be understood to require no moreof the external system than that able to produce and receive messages asrequired by the process component that interacts with the externalsystem. For example, process components may include multiple operationsthat may provide interaction with the external system. Each operationgenerally belongs to one type of process component in the architecture.Operations can be synchronous or asynchronous, corresponding tosynchronous or asynchronous process agents, which will be describedbelow. The operation is often the smallest, separately-callablefunction, described by a set of data types used as input, output, andfault parameters serving as a signature.

The architectural elements may also include the service interface,referred to simply as the interface. The interface is a named group ofoperations. The interface often belongs to one process component andprocess component might contain multiple interfaces. In oneimplementation, the service interface contains only inbound or outboundoperations, but not a mixture of both. One interface can contain bothsynchronous and asynchronous operations. Normally, operations of thesame type (either inbound or outbound) which belong to the same messagechoreography will belong to the same interface. Thus, generally, alloutbound operations to the same other process component are in oneinterface.

The architectural elements also include the message. Operations transmitand receive messages. Any convenient messaging infrastructure can beused. A message is information conveyed from one process componentinstance to another, with the expectation that activity will ensue.Operation can use multiple message types for inbound, outbound, or errormessages. When two process components are in different deployment units,invocation of an operation of one process component by the other processcomponent is accomplished by the operation on the other processcomponent sending a message to the first process component.

The architectural elements may also include the process agent. Processagents do business processing that involves the sending or receiving ofmessages. Each operation normally has at least one associated processagent. Each process agent can be associated with one or more operations.Process agents can be either inbound or outbound and either synchronousor asynchronous. Asynchronous outbound process agents are called after abusiness object changes such as after a “create”, “update”, or “delete”of a business object instance. Synchronous outbound process agents aregenerally triggered directly by business object. An outbound processagent will generally perform some processing of the data of the businessobject instance whose change triggered the event. The outbound agenttriggers subsequent business process steps by sending messages usingwell-defined outbound services to another process component, whichgenerally will be in another deployment unit, or to an external system.The outbound process agent is linked to the one business object thattriggers the agent, but it is sent not to another business object butrather to another process component. Thus, the outbound process agentcan be implemented without knowledge of the exact business object designof the recipient process component. Alternatively, the process agent maybe inbound. For example, inbound process agents may be used for theinbound part of a message-based communication. Inbound process agentsare called after a message has been received. The inbound process agentstarts the execution of the business process step requested in a messageby creating or updating one or multiple business object instances.Inbound process agent is not generally the agent of business object butof its process component. Inbound process agent can act on multiplebusiness objects in a process component. Regardless of whether theprocess agent is inbound or outbound, an agent may be synchronous ifused when a process component requires a more or less immediate responsefrom another process component, and is waiting for that response tocontinue its work.

The architectural elements also include the deployment unit. Eachdeployment unit may include one or more process components that aregenerally deployed together on a single computer system platform.Conversely, separate deployment units can be deployed on separatephysical computing systems. The process components of one deploymentunit can interact with those of another deployment unit using messagespassed through one or more data communication networks or other suitablecommunication channels. Thus, a deployment unit deployed on a platformbelonging to one business can interact with a deployment unit softwareentity deployed on a separate platform belonging to a different andunrelated business, allowing for business-to-business communication.More than one instance of a given deployment unit can execute at thesame time, on the same computing system or on separate physicalcomputing systems. This arrangement allows the functionality offered bythe deployment unit to be scaled to meet demand by creating as manyinstances as needed.

Since interaction between deployment units is through process componentoperations, one deployment unit can be replaced by other anotherdeployment unit as long as the new deployment unit supports theoperations depended upon by other deployment units as appropriate. Thus,while deployment units can depend on the external interfaces of processcomponents in other deployment units, deployment units are not dependenton process component interaction within other deployment units.Similarly, process components that interact with other processcomponents or external systems only through messages, e.g., as sent andreceived by operations, can also be replaced as long as the replacementgenerally supports the operations of the original.

Services (or interfaces) may be provided in a flexible architecture tosupport varying criteria between services and systems. The flexiblearchitecture may generally be provided by a service delivery businessobject. The system may be able to schedule a service asynchronously asnecessary, or on a regular basis. Services may be planned according to aschedule manually or automatically. For example, a follow-up service maybe scheduled automatically upon completing an initial service. Inaddition, flexible execution periods may be possible (e.g. hourly,daily, every three months, etc.). Each customer may plan the services ondemand or reschedule service execution upon request.

FIG. 1 depicts a flow diagram 100 showing an example technique, perhapsimplemented by systems similar to those disclosed herein. Initially, togenerate the business object model, design engineers study the detailsof a business process, and model the business process using a “businessscenario” (step 102). The business scenario identifies the stepsperformed by the different business entities during a business process.Thus, the business scenario is a complete representation of a clearlydefined business process.

After creating the business scenario, the developers add details to eachstep of the business scenario (step 104). In particular, for each stepof the business scenario, the developers identify the complete processsteps performed by each business entity. A discrete portion of thebusiness scenario reflects a “business transaction,” and each businessentity is referred to as a “component” of the business transaction. Thedevelopers also identify the messages that are transmitted between thecomponents. A “process interaction model” represents the completeprocess steps between two components.

After creating the process interaction model, the developers create a“message choreography” (step 106), which depicts the messagestransmitted between the two components in the process interaction model.The developers then represent the transmission of the messages betweenthe components during a business process in a “business document flow”(step 108). Thus, the business document flow illustrates the flow ofinformation between the business entities during a business process.

FIG. 2 depicts an example business document flow 200 for the process ofpurchasing a product or service. The business entities involved with theillustrative purchase process include Accounting 202, Payment 204,Invoicing 206, Supply Chain Execution (“SCE”) 208, Supply Chain Planning(“SCP”) 210, Fulfillment Coordination (“FC”) 212, Supply RelationshipManagement (“SRM”) 214, Supplier 216, and Bank 218. The businessdocument flow 200 is divided into four different transactions:Preparation of Ordering (“Contract”) 220, Ordering 222, Goods Receiving(“Delivery”) 224, and Billing/Payment 226. In the business documentflow, arrows 228 represent the transmittal of documents. Each documentreflects a message transmitted between entities. One of ordinary skillin the art will appreciate that the messages transferred may beconsidered to be a communications protocol. The process flow follows thefocus of control, which is depicted as a solid vertical line (e.g., 229)when the step is required, and a dotted vertical line (e.g., 230) whenthe step is optional.

During the Contract transaction 220, the SRM 214 sends a Source ofSupply Notification 232 to the SCP 210. This step is optional, asillustrated by the optional control line 230 coupling this step to theremainder of the business document flow 200. During the Orderingtransaction 222, the SCP 210 sends a Purchase Requirement Request 234 tothe FC 212, which forwards a Purchase Requirement Request 236 to the SRM214. The SRM 214 then sends a Purchase Requirement Confirmation 238 tothe FC 212, and the FC 212 sends a Purchase Requirement Confirmation 240to the SCP 210. The SRM 214 also sends a Purchase Order Request 242 tothe Supplier 216, and sends Purchase Order Information 244 to the FC212. The FC 212 then sends a Purchase Order Planning Notification 246 tothe SCP 210. The Supplier 216, after receiving the Purchase OrderRequest 242, sends a Purchase Order Confirmation 248 to the SRM 214,which sends a Purchase Order Information confirmation message 254 to theFC 212, which sends a message 256 confirming the Purchase Order PlanningNotification to the SCP 210. The SRM 214 then sends an Invoice DueNotification 258 to Invoicing 206.

During the Delivery transaction 224, the FC 212 sends a DeliveryExecution Request 260 to the SCE 208. The Supplier 216 could optionally(illustrated at control line 250) send a Dispatched DeliveryNotification 252 to the SCE 208. The SCE 208 then sends a message 262 tothe FC 212 notifying the FC 212 that the request for the DeliveryInformation was created. The FC 212 then sends a message 264 notifyingthe SRM 214 that the request for the Delivery Information was created.The FC 212 also sends a message 266 notifying the SCP 210 that therequest for the Delivery Information was created. The SCE 208 sends amessage 268 to the FC 212 when the goods have been set aside fordelivery. The FC 212 sends a message 270 to the SRM 214 when the goodshave been set aside for delivery. The FC 212 also sends a message 272 tothe SCP 210 when the goods have been set aside for delivery.

The SCE 208 sends a message 274 to the FC 212 when the goods have beendelivered. The FC 212 then sends a message 276 to the SRM 214 indicatingthat the goods have been delivered, and sends a message 278 to the SCP210 indicating that the goods have been delivered. The SCE 208 thensends an Inventory Change Accounting Notification 280 to Accounting 202,and an Inventory Change Notification 282 to the SCP 210. The FC 212sends an Invoice Due Notification 284 to Invoicing 206, and SCE 208sends a Received Delivery Notification 286 to the Supplier 216.

During the Billing/Payment transaction 226, the Supplier 216 sends anInvoice Request 287 to Invoicing 206. Invoicing 206 then sends a PaymentDue Notification 288 to Payment 204, a Tax Due Notification 289 toPayment 204, an Invoice Confirmation 290 to the Supplier 216, and anInvoice Accounting Notification 291 to Accounting 202. Payment 204 sendsa Payment Request 292 to the Bank 218, and a Payment RequestedAccounting Notification 293 to Accounting 202. Bank 218 sends a BankStatement Information 296 to Payment 204. Payment 204 then sends aPayment Done Information 294 to Invoicing 206 and a Payment DoneAccounting Notification 295 to Accounting 202.

Within a business document flow, business documents having the same orsimilar structures are marked. For example, in the business documentflow 200 depicted in FIG. 2, Purchase Requirement Requests 234, 236 andPurchase Requirement Confirmations 238, 240 have the same structures.Thus, each of these business documents is marked with an “O6.”Similarly, Purchase Order Request 242 and Purchase Order Confirmation248 have the same structures. Thus, both documents are marked with an“O1.” Each business document or message is based on a message type.

From the business document flow, the developers identify the businessdocuments having identical or similar structures, and use these businessdocuments to create the business object model (step 110). The businessobject model includes the objects contained within the businessdocuments. These objects are reflected as packages containing relatedinformation, and are arranged in a hierarchical structure within thebusiness object model, as discussed below.

Methods and systems consistent with the subject matter described hereinthen generate interfaces from the business object model (step 112). Theheterogeneous programs use instantiations of these interfaces (called“business document objects” below) to create messages (step 114), whichare sent to complete the business transaction (step 116). Businessentities use these messages to exchange information with other businessentities during an end-to-end business transaction. Since the businessobject model is shared by heterogeneous programs, the interfaces areconsistent among these programs. The heterogeneous programs use theseconsistent interfaces to communicate in a consistent manner, thusfacilitating the business transactions.

Standardized Business-to-Business (“B2B”) messages are compliant with atleast one of the e-business standards (i.e., they include thebusiness-relevant fields of the standard). The e-business standardsinclude, for example, RosettaNet for the high-tech industry, ChemicalIndustry Data Exchange (“CIDX”), Petroleum Industry Data Exchange(“PIDX”) for the oil industry, UCCnet for trade, PapiNet for the paperindustry, Odette for the automotive industry, HR-XML for humanresources, and XML Common Business Library (“xCBL”). Thus, B2B messagesenable simple integration of components in heterogeneous systemlandscapes. Application-to-Application (“A2A”) messages often exceed thestandards and thus may provide the benefit of the full functionality ofapplication components. Although various steps of FIG. 1 were describedas being performed manually, one skilled in the art will appreciate thatsuch steps could be computer-assisted or performed entirely by acomputer, including being performed by either hardware, software, or anyother combination thereof.

B. Implementation Details

As discussed above, methods and systems consistent with the subjectmatter described herein create consistent interfaces by generating theinterfaces from a business object model. Details regarding the creationof the business object model, the generation of an interface from thebusiness object model, and the use of an interface generated from thebusiness object model are provided below.

Turning to the illustrated embodiment in FIG. 3A, environment 300includes or is communicably coupled (such as via a one-, bi- ormulti-directional link or network) with server 302, one or more clients304, one or more or vendors 306, one or more customers 308, at leastsome of which communicate across network 312. But, of course, thisillustration is for example purposes only, and any distributed system orenvironment implementing one or more of the techniques described hereinmay be within the scope of this disclosure. Server 302 comprises anelectronic computing device operable to receive, transmit, process andstore data associated with environment 300. Generally, FIG. 3A providesmerely one example of computers that may be used with the disclosure.Each computer is generally intended to encompass any suitable processingdevice. For example, although FIG. 3A illustrates one server 302 thatmay be used with the disclosure, environment 300 can be implementedusing computers other than servers, as well as a server pool. Indeed,server 302 may be any computer or processing device such as, forexample, a blade server, general-purpose personal computer (PC),Macintosh, workstation, Unix-based computer, or any other suitabledevice. In other words, the present disclosure contemplates computersother than general purpose computers as well as computers withoutconventional operating systems. Server 302 may be adapted to execute anyoperating system including Linux, UNIX, Windows Server, or any othersuitable operating system. According to one embodiment, server 302 mayalso include or be communicably coupled with a web server and/or a mailserver.

As illustrated (but not required), the server 302 is communicablycoupled with a relatively remote repository 335 over a portion of thenetwork 312. The repository 335 is any electronic storage facility, dataprocessing center, or archive that may supplement or replace localmemory (such as 327). The repository 335 may be a central databasecommunicably coupled with the one or more servers 302 and the clients304 via a virtual private network (VPN), SSH (Secure Shell) tunnel, orother secure network connection. The repository 335 may be physically orlogically located at any appropriate location including in one of theexample enterprises or off-shore, so long as it remains operable tostore information associated with the environment 300 and communicatesuch data to the server 302 or at least a subset of plurality of theclients 304.

Illustrated server 302 includes local memory 327. Memory 327 may includeany memory or database module and may take the form of volatile ornon-volatile memory including, without limitation, magnetic media,optical media, random access memory (RAM), read-only memory (ROM),removable media, or any other suitable local or remote memory component.Illustrated memory 327 includes an exchange infrastructure (“XI”) 314,which is an infrastructure that supports the technical interaction ofbusiness processes across heterogeneous system environments. XI 314centralizes the communication between components within a businessentity and between different business entities. When appropriate, XI 314carries out the mapping between the messages. XI 314 integratesdifferent versions of systems implemented on different platforms (e.g.,Java and ABAP). XI 314 is based on an open architecture, and makes useof open standards, such as eXtensible Markup Language (XML)™ and Javaenvironments. XI 314 offers services that are useful in a heterogeneousand complex system landscape. In particular, XI 314 offers a runtimeinfrastructure for message exchange, configuration options for managingbusiness processes and message flow, and options for transformingmessage contents between sender and receiver systems.

XI 314 stores data types 316, a business object model 318, andinterfaces 320. The details regarding the business object model aredescribed below. Data types 316 are the building blocks for the businessobject model 318. The business object model 318 is used to deriveconsistent interfaces 320. XI 314 allows for the exchange of informationfrom a first company having one computer system to a second companyhaving a second computer system over network 312 by using thestandardized interfaces 320.

While not illustrated, memory 327 may also include business objects andany other appropriate data such as services, interfaces, VPNapplications or services, firewall policies, a security or access log,print or other reporting files, HTML files or templates, data classes orobject interfaces, child software applications or sub-systems, andothers. This stored data may be stored in one or more logical orphysical repositories. In some embodiments, the stored data (or pointersthereto) may be stored in one or more tables in a relational databasedescribed in terms of SQL statements or scripts. In the same or otherembodiments, the stored data may also be formatted, stored, or definedas various data structures in text files, XML documents, Virtual StorageAccess Method (VSAM) files, flat files, Btrieve files,comma-separated-value (CSV) files, internal variables, or one or morelibraries. For example, a particular data service record may merely be apointer to a particular piece of third party software stored remotely.In another example, a particular data service may be an internallystored software object usable by authenticated customers or internaldevelopment. In short, the stored data may comprise one table or file ora plurality of tables or files stored on one computer or across aplurality of computers in any appropriate format. Indeed, some or all ofthe stored data may be local or remote without departing from the scopeof this disclosure and store any type of appropriate data.

Server 302 also includes processor 325. Processor 325 executesinstructions and manipulates data to perform the operations of server302 such as, for example, a central processing unit (CPU), a blade, anapplication specific integrated circuit (ASIC), or a field-programmablegate array (FPGA). Although FIG. 3A illustrates a single processor 325in server 302, multiple processors 325 may be used according toparticular needs and reference to processor 325 is meant to includemultiple processors 325 where applicable. In the illustrated embodiment,processor 325 executes at least business application 330.

At a high level, business application 330 is any application, program,module, process, or other software that utilizes or facilitates theexchange of information via messages (or services) or the use ofbusiness objects. For example, application 330 may implement, utilize orotherwise leverage an enterprise service-oriented architecture(enterprise SOA), which may be considered a blueprint for an adaptable,flexible, and open IT architecture for developing services-based,enterprise-scale business solutions. This example enterprise service maybe a series of web services combined with business logic that can beaccessed and used repeatedly to support a particular business process.Aggregating web services into business-level enterprise services helpsprovide a more meaningful foundation for the task of automatingenterprise-scale business scenarios Put simply, enterprise services helpprovide a holistic combination of actions that are semantically linkedto complete the specific task, no matter how many cross-applications areinvolved. In certain cases, environment 300 may implement a compositeapplication 330, as described below in FIG. 4. Regardless of theparticular implementation, “software” may include software, firmware,wired or programmed hardware, or any combination thereof as appropriate.Indeed, application 330 may be written or described in any appropriatecomputer language including C, C++, Java, Visual Basic, assembler, Perl,any suitable version of 4GL, as well as others. For example, returningto the above mentioned composite application, the composite applicationportions may be implemented as Enterprise Java Beans (EJBs) or thedesign-time components may have the ability to generate run-timeimplementations into different platforms, such as J2EE (Java 2 Platform,Enterprise Edition), ABAP (Advanced Business Application Programming)objects, or Microsoft's .NET. It will be understood that whileapplication 330 is illustrated in FIG. 4 as including varioussub-modules, application 330 may include numerous other sub-modules ormay instead be a single multi-tasked module that implements the variousfeatures and functionality through various objects, methods, or otherprocesses. Further, while illustrated as internal to server 302, one ormore processes associated with application 330 may be stored,referenced, or executed remotely. For example, a portion of application330 may be a web service that is remotely called, while another portionof application 330 may be an interface object bundled for processing atremote client 304. Moreover, application 330 may be a child orsub-module of another software module or enterprise application (notillustrated) without departing from the scope of this disclosure.Indeed, application 330 may be a hosted solution that allows multiplerelated or third parties in different portions of the process to performthe respective processing.

More specifically, as illustrated in FIG. 4, application 330 may be acomposite application, or an application built on other applications,that includes an object access layer (OAL) and a service layer. In thisexample, application 330 may execute or provide a number of applicationservices, such as customer relationship management (CRM) systems, humanresources management (HRM) systems, financial management (FM) systems,project management (PM) systems, knowledge management (KM) systems, andelectronic file and mail systems. Such an object access layer isoperable to exchange data with a plurality of enterprise base systemsand to present the data to a composite application through a uniforminterface. The example service layer is operable to provide services tothe composite application. These layers may help the compositeapplication to orchestrate a business process in synchronization withother existing processes (e.g., native processes of enterprise basesystems) and leverage existing investments in the IT platform. Further,composite application 330 may run on a heterogeneous IT platform. Indoing so, composite application may be cross-functional in that it maydrive business processes across different applications, technologies,and organizations. Accordingly, composite application 330 may driveend-to-end business processes across heterogeneous systems orsub-systems. Application 330 may also include or be coupled with apersistence layer and one or more application system connectors. Suchapplication system connectors enable data exchange and integration withenterprise sub-systems and may include an Enterprise Connector (EC)interface, an Internet Communication Manager/Internet CommunicationFramework (ICM/ICF) interface, an Encapsulated PostScript (EPS)interface, and/or other interfaces that provide Remote Function Call(RFC) capability. It will be understood that while this exampledescribes a composite application 330, it may instead be a standalone or(relatively) simple software program. Regardless, application 330 mayalso perform processing automatically, which may indicate that theappropriate processing is substantially performed by at least onecomponent of environment 300. It should be understood that automaticallyfurther contemplates any suitable administrator or other userinteraction with application 330 or other components of environment 300without departing from the scope of this disclosure.

Returning to FIG. 3A, illustrated server 302 may also include interface317 for communicating with other computer systems, such as clients 304,over network 312 in a client-server or other distributed environment. Incertain embodiments, server 302 receives data from internal or externalsenders through interface 317 for storage in memory 327, for storage inDB 335, and/or processing by processor 325. Generally, interface 317comprises logic encoded in software and/or hardware in a suitablecombination and operable to communicate with network 312. Morespecifically, interface 317 may comprise software supporting one or morecommunications protocols associated with communications network 312 orhardware operable to communicate physical signals.

Network 312 facilitates wireless or wireline communication betweencomputer server 302 and any other local or remote computer, such asclients 304. Network 312 may be all or a portion of an enterprise orsecured network. In another example, network 312 may be a VPN merelybetween server 302 and client 304 across wireline or wireless link. Suchan example wireless link may be via 802.11a, 802.11b, 802.11g, 802.20,WiMax, and many others. While illustrated as a single or continuousnetwork, network 312 may be logically divided into various sub-nets orvirtual networks without departing from the scope of this disclosure, solong as at least portion of network 312 may facilitate communicationsbetween server 302 and at least one client 304. For example, server 302may be communicably coupled to one or more “local” repositories throughone sub-net while communicably coupled to a particular client 304 or“remote” repositories through another. In other words, network 312encompasses any internal or external network, networks, sub-network, orcombination thereof operable to facilitate communications betweenvarious computing components in environment 300. Network 312 maycommunicate, for example, Internet Protocol (IP) packets, Frame Relayframes, Asynchronous Transfer Mode (ATM) cells, voice, video, data, andother suitable information between network addresses. Network 312 mayinclude one or more local area networks (LANs), radio access networks(RANs), metropolitan area networks (MANs), wide area networks (WANs),all or a portion of the global computer network known as the Internet,and/or any other communication system or systems at one or morelocations. In certain embodiments, network 312 may be a secure networkassociated with the enterprise and certain local or remote vendors 306and customers 308. As used in this disclosure, customer 308 is anyperson, department, organization, small business, enterprise, or anyother entity that may use or request others to use environment 300. Asdescribed above, vendors 306 also may be local or remote to customer308. Indeed, a particular vendor 306 may provide some content tobusiness application 330, while receiving or purchasing other content(at the same or different times) as customer 308. As illustrated,customer 308 and vendor 06 each typically perform some processing (suchas uploading or purchasing content) using a computer, such as client304.

Client 304 is any computing device operable to connect or communicatewith server 302 or network 312 using any communication link. Forexample, client 304 is intended to encompass a personal computer, touchscreen terminal, workstation, network computer, kiosk, wireless dataport, smart phone, personal data assistant (PDA), one or more processorswithin these or other devices, or any other suitable processing deviceused by or for the benefit of business 308, vendor 306, or some otheruser or entity. At a high level, each client 304 includes or executes atleast GUI 336 and comprises an electronic computing device operable toreceive, transmit, process and store any appropriate data associatedwith environment 300. It will be understood that there may be any numberof clients 304 communicably coupled to server 302. Further, “client304,” “business,” “business analyst,” “end user,” and “user” may be usedinterchangeably as appropriate without departing from the scope of thisdisclosure. Moreover, for ease of illustration, each client 304 isdescribed in terms of being used by one user. But this disclosurecontemplates that many users may use one computer or that one user mayuse multiple computers. For example, client 304 may be a PDA operable towirelessly connect with external or unsecured network. In anotherexample, client 304 may comprise a laptop that includes an input device,such as a keypad, touch screen, mouse, or other device that can acceptinformation, and an output device that conveys information associatedwith the operation of server 302 or clients 304, including digital data,visual information, or GUI 336. Both the input device and output devicemay include fixed or removable storage media such as a magnetic computerdisk, CD-ROM, or other suitable media to both receive input from andprovide output to users of clients 304 through the display, namely theclient portion of GUI or application interface 336.

GUI 336 comprises a graphical user interface operable to allow the userof client 304 to interface with at least a portion of environment 300for any suitable purpose, such as viewing application or othertransaction data. Generally, GUI 336 provides the particular user withan efficient and user-friendly presentation of data provided by orcommunicated within environment 300. For example, GUI 336 may presentthe user with the components and information that is relevant to theirtask, increase reuse of such components, and facilitate a sizabledeveloper community around those components. GUI 336 may comprise aplurality of customizable frames or views having interactive fields,pull-down lists, and buttons operated by the user. For example, GUI 336is operable to display data involving business objects and interfaces ina user-friendly form based on the user context and the displayed data.In another example, GUI 336 is operable to display different levels andtypes of information involving business objects and interfaces based onthe identified or supplied user role. GUI 336 may also present aplurality of portals or dashboards. For example, GUI 336 may display aportal that allows users to view, create, and manage historical andreal-time reports including role-based reporting and such. Of course,such reports may be in any appropriate output format including PDF,HTML, and printable text. Real-time dashboards often provide table andgraph information on the current state of the data, which may besupplemented by business objects and interfaces. It should be understoodthat the term graphical user interface may be used in the singular or inthe plural to describe one or more graphical user interfaces and each ofthe displays of a particular graphical user interface. Indeed, referenceto GUI 336 may indicate a reference to the front-end or a component ofbusiness application 330, as well as the particular interface accessiblevia client 304, as appropriate, without departing from the scope of thisdisclosure. Therefore, GUI 336 contemplates any graphical userinterface, such as a generic web browser or touchscreen, that processesinformation in environment 300 and efficiently presents the results tothe user. Server 302 can accept data from client 304 via the web browser(e.g., Microsoft Internet Explorer or Netscape Navigator) and return theappropriate HTML or XML responses to the browser using network 312.

More generally in environment 300 as depicted in FIG. 3B, a FoundationLayer 375 can be deployed on multiple separate and distinct hardwareplatforms, e.g., System A 350 and System B 360, to support applicationsoftware deployed as two or more deployment units distributed on theplatforms, including deployment unit 352 deployed on System A anddeployment unit 362 deployed on System B. In this example, thefoundation layer can be used to support application software deployed inan application layer. In particular, the foundation layer can be used inconnection with application software implemented in accordance with asoftware architecture that provides a suite of enterprise serviceoperations having various application functionality. In someimplementations, the application software is implemented to be deployedon an application platform that includes a foundation layer thatcontains all fundamental entities that can used from multiple deploymentunits. These entities can be process components, business objects, andreuse service components. A reuse service component is a piece ofsoftware that is reused in different transactions. A reuse servicecomponent is used by its defined interfaces, which can be, e.g., localAPIs or service interfaces. As explained above, process components inseparate deployment units interact through service operations, asillustrated by messages passing between service operations 356 and 366,which are implemented in process components 354 and 364, respectively,which are included in deployment units 352 and 362, respectively. Asalso explained above, some form of direct communication is generally theform of interaction used between a business object, e.g., businessobject 358 and 368, of an application deployment unit and a businessobject, such as master data object 370, of the Foundation Layer 375.

Various components of the present disclosure may be modeled using amodel-driven environment. For example, the model-driven framework orenvironment may allow the developer to use simple drag-and-droptechniques to develop pattern-based or freestyle user interfaces anddefine the flow of data between them. The result could be an efficient,customized, visually rich online experience. In some cases, thismodel-driven development may accelerate the application developmentprocess and foster business-user self-service. It further enablesbusiness analysts or IT developers to compose visually rich applicationsthat use analytic services, enterprise services, remote function calls(RFCs), APIs, and stored procedures. In addition, it may allow them toreuse existing applications and create content using a modeling processand a visual user interface instead of manual coding.

FIG. 5A depicts an example modeling environment 516, namely a modelingenvironment, in accordance with one embodiment of the presentdisclosure. Thus, as illustrated in FIG. 5A, such a modeling environment516 may implement techniques for decoupling models created duringdesign-time from the runtime environment. In other words, modelrepresentations for GUIs created in a design time environment aredecoupled from the runtime environment in which the GUIs are executed.Often in these environments, a declarative and executable representationfor GUIs for applications is provided that is independent of anyparticular runtime platform, GUI framework, device, or programminglanguage.

According to some embodiments, a modeler (or other analyst) may use themodel-driven modeling environment 516 to create pattern-based orfreestyle user interfaces using simple drag-and-drop services. Becausethis development may be model-driven, the modeler can typically composean application using models of business objects without having to writemuch, if any, code. In some cases, this example modeling environment 516may provide a personalized, secure interface that helps unify enterpriseapplications, information, and processes into a coherent, role-basedportal experience. Further, the modeling environment 516 may allow thedeveloper to access and share information and applications in acollaborative environment. In this way, virtual collaboration roomsallow developers to work together efficiently, regardless of where theyare located, and may enable powerful and immediate communication thatcrosses organizational boundaries while enforcing security requirements.Indeed, the modeling environment 516 may provide a shared set ofservices for finding, organizing, and accessing unstructured contentstored in third-party repositories and content management systems acrossvarious networks 312. Classification tools may automate the organizationof information, while subject-matter experts and content managers canpublish information to distinct user audiences. Regardless of theparticular implementation or architecture, this modeling environment 516may allow the developer to easily model hosted business objects 140using this model-driven approach.

In certain embodiments, the modeling environment 516 may implement orutilize a generic, declarative, and executable GUI language (generallydescribed as XGL). This example XGL is generally independent of anyparticular GUI framework or runtime platform. Further, XGL is normallynot dependent on characteristics of a target device on which the graphicuser interface is to be displayed and may also be independent of anyprogramming language. XGL is used to generate a generic representation(occasionally referred to as the XGL representation or XGL-compliantrepresentation) for a design-time model representation. The XGLrepresentation is thus typically a device-independent representation ofa GUI. The XGL representation is declarative in that the representationdoes not depend on any particular GUI framework, runtime platform,device, or programming language. The XGL representation can beexecutable and therefore can unambiguously encapsulate executionsemantics for the GUI described by a model representation. In short,models of different types can be transformed to XGL representations.

The XGL representation may be used for generating representations ofvarious different GUIs and supports various GUI features including fullwindowing and componentization support, rich data visualizations andanimations, rich modes of data entry and user interactions, and flexibleconnectivity to any complex application data services. While a specificembodiment of XGL is discussed, various other types of XGLs may also beused in alternative embodiments. In other words, it will be understoodthat XGL is used for example description only and may be read to includeany abstract or modeling language that can be generic, declarative, andexecutable.

Turning to the illustrated embodiment in FIG. 5A, modeling tool 340 maybe used by a GUI designer or business analyst during the applicationdesign phase to create a model representation 502 for a GUI application.It will be understood that modeling environment 516 may include or becompatible with various different modeling tools 340 used to generatemodel representation 502. This model representation 502 may be amachine-readable representation of an application or a domain specificmodel. Model representation 502 generally encapsulates various designparameters related to the GUI such as GUI components, dependenciesbetween the GUI components, inputs and outputs, and the like. Putanother way, model representation 502 provides a form in which the oneor more models can be persisted and transported, and possibly handled byvarious tools such as code generators, runtime interpreters, analysisand validation tools, merge tools, and the like. In one embodiment,model representation 502 maybe a collection of XML documents with awell-formed syntax.

Illustrated modeling environment 516 also includes an abstractrepresentation generator (or XGL generator) 504 operable to generate anabstract representation (for example, XGL representation orXGL-compliant representation) 506 based upon model representation 502.Abstract representation generator 504 takes model representation 502 asinput and outputs abstract representation 506 for the modelrepresentation. Model representation 502 may include multiple instancesof various forms or types depending on the tool/language used for themodeling. In certain cases, these various different modelrepresentations may each be mapped to one or more abstractrepresentations 506. Different types of model representations may betransformed or mapped to XGL representations. For each type of modelrepresentation, mapping rules may be provided for mapping the modelrepresentation to the XGL representation 506. Different mapping rulesmay be provided for mapping a model representation to an XGLrepresentation.

This XGL representation 506 that is created from a model representationmay then be used for processing in the runtime environment. For example,the XGL representation 506 may be used to generate a machine-executableruntime GUI (or some other runtime representation) that may be executedby a target device. As part of the runtime processing, the XGLrepresentation 506 may be transformed into one or more runtimerepresentations, which may indicate source code in a particularprogramming language, machine-executable code for a specific runtimeenvironment, executable GUI, and so forth, which may be generated forspecific runtime environments and devices. Since the XGL representation506, rather than the design-time model representation, is used by theruntime environment, the design-time model representation is decoupledfrom the runtime environment. The XGL representation 506 can thus serveas the common ground or interface between design-time user interfacemodeling tools and a plurality of user interface runtime frameworks. Itprovides a self-contained, closed, and deterministic definition of allaspects of a graphical user interface in a device-independent andprogramming-language independent manner. Accordingly, abstractrepresentation 506 generated for a model representation 502 is generallydeclarative and executable in that it provides a representation of theGUI of model representation 502 that is not dependent on any device orruntime platform, is not dependent on any programming language, andunambiguously encapsulates execution semantics for the GUI. Theexecution semantics may include, for example, identification of variouscomponents of the GUI, interpretation of connections between the variousGUI components, information identifying the order of sequencing ofevents, rules governing dynamic behavior of the GUI, rules governinghandling of values by the GUI, and the like. The abstract representation506 is also not GUI runtime-platform specific. The abstractrepresentation 506 provides a self-contained, closed, and deterministicdefinition of all aspects of a graphical user interface that is deviceindependent and language independent.

Abstract representation 506 is such that the appearance and executionsemantics of a GUI generated from the XGL representation workconsistently on different target devices irrespective of the GUIcapabilities of the target device and the target device platform. Forexample, the same XGL representation may be mapped to appropriate GUIson devices of differing levels of GUI complexity (i.e., the sameabstract representation may be used to generate a GUI for devices thatsupport simple GUIs and for devices that can support complex GUIs), theGUI generated by the devices are consistent with each other in theirappearance and behavior.

Abstract representation generator 504 may be configured to generateabstract representation 506 for models of different types, which may becreated using different modeling tools 340. It will be understood thatmodeling environment 516 may include some, none, or other sub-modules orcomponents as those shown in this example illustration. In other words,modeling environment 516 encompasses the design-time environment (withor without the abstract generator or the various representations), amodeling toolkit (such as 340) linked with a developer's space, or anyother appropriate software operable to decouple models created duringdesign-time from the runtime environment. Abstract representation 506provides an interface between the design time environment and theruntime environment. As shown, this abstract representation 506 may thenbe used by runtime processing.

As part of runtime processing, modeling environment 516 may includevarious runtime tools 508 and may generate different types of runtimerepresentations based upon the abstract representation 506. Examples ofruntime representations include device or language-dependent (orspecific) source code, runtime platform-specific machine-readable code,GUIs for a particular target device, and the like. The runtime tools 508may include compilers, interpreters, source code generators, and othersuch tools that are configured to generate runtime platform-specific ortarget device-specific runtime representations of abstractrepresentation 506. The runtime tool 508 may generate the runtimerepresentation from abstract representation 506 using specific rulesthat map abstract representation 506 to a particular type of runtimerepresentation. These mapping rules may be dependent on the type ofruntime tool, characteristics of the target device to be used fordisplaying the GUI, runtime platform, and/or other factors. Accordingly,mapping rules may be provided for transforming the abstractrepresentation 506 to any number of target runtime representationsdirected to one or more target GUI runtime platforms. For example,XGL-compliant code generators may conform to semantics of XGL, asdescribed below. XGL-compliant code generators may ensure that theappearance and behavior of the generated user interfaces is preservedacross a plurality of target GUI frameworks, while accommodating thedifferences in the intrinsic characteristics of each and alsoaccommodating the different levels of capability of target devices.

For example, as depicted in example FIG. 5A, an XGL-to-Java compiler508A may take abstract representation 506 as input and generate Javacode 510 for execution by a target device comprising a Java runtime 512.Java runtime 512 may execute Java code 510 to generate or display a GUI514 on a Java-platform target device. As another example, anXGL-to-Flash compiler 508B may take abstract representation 506 as inputand generate Flash code 526 for execution by a target device comprisinga Flash runtime 518. Flash runtime 518 may execute Flash code 516 togenerate or display a GUI 520 on a target device comprising a Flashplatform. As another example, an XGL-to-DHTML (dynamic HTML) interpreter508C may take abstract representation 506 as input and generate DHTMLstatements (instructions) on the fly which are then interpreted by aDHTML runtime 522 to generate or display a GUI 524 on a target devicecomprising a DHTML platform.

It should be apparent that abstract representation 506 may be used togenerate GUIs for Extensible Application Markup Language (XAML) orvarious other runtime platforms and devices. The same abstractrepresentation 506 may be mapped to various runtime representations anddevice-specific and runtime platform-specific GUIs. In general, in theruntime environment, machine executable instructions specific to aruntime environment may be generated based upon the abstractrepresentation 506 and executed to generate a GUI in the runtimeenvironment. The same XGL representation may be used to generate machineexecutable instructions specific to different runtime environments andtarget devices.

According to certain embodiments, the process of mapping a modelrepresentation 502 to an abstract representation 506 and mapping anabstract representation 506 to some runtime representation may beautomated. For example, design tools may automatically generate anabstract representation for the model representation using XGL and thenuse the XGL abstract representation to generate GUIs that are customizedfor specific runtime environments and devices. As previously indicated,mapping rules may be provided for mapping model representations to anXGL representation. Mapping rules may also be provided for mapping anXGL representation to a runtime platform-specific representation.

Since the runtime environment uses abstract representation 506 ratherthan model representation 502 for runtime processing, the modelrepresentation 502 that is created during design-time is decoupled fromthe runtime environment. Abstract representation 506 thus provides aninterface between the modeling environment and the runtime environment.As a result, changes may be made to the design time environment,including changes to model representation 502 or changes that affectmodel representation 502, generally to not substantially affect orimpact the runtime environment or tools used by the runtime environment.Likewise, changes may be made to the runtime environment generally tonot substantially affect or impact the design time environment. Adesigner or other developer can thus concentrate on the design aspectsand make changes to the design without having to worry about the runtimedependencies such as the target device platform or programming languagedependencies.

FIG. 5B depicts an example process for mapping a model representation502 to a runtime representation using the example modeling environment516 of FIG. 5A or some other modeling environment. Model representation502 may comprise one or more model components and associated propertiesthat describe a data object, such as hosted business objects andinterfaces. As described above, at least one of these model componentsis based on or otherwise associated with these hosted business objectsand interfaces. The abstract representation 506 is generated based uponmodel representation 502. Abstract representation 506 may be generatedby the abstract representation generator 504. Abstract representation506 comprises one or more abstract GUI components and propertiesassociated with the abstract GUI components. As part of generation ofabstract representation 506, the model GUI components and theirassociated properties from the model representation are mapped toabstract GUI components and properties associated with the abstract GUIcomponents. Various mapping rules may be provided to facilitate themapping. The abstract representation encapsulates both appearance andbehavior of a GUI. Therefore, by mapping model components to abstractcomponents, the abstract representation not only specifies the visualappearance of the GUI but also the behavior of the GUI, such as inresponse to events whether clicking/dragging or scrolling, interactionsbetween GUI components and such.

One or more runtime representations 550 a, including GUIs for specificruntime environment platforms, may be generated from abstractrepresentation 506. A device-dependent runtime representation may begenerated for a particular type of target device platform to be used forexecuting and displaying the GUI encapsulated by the abstractrepresentation. The GUIs generated from abstract representation 506 maycomprise various types of GUI elements such as buttons, windows,scrollbars, input boxes, etc. Rules may be provided for mapping anabstract representation to a particular runtime representation. Variousmapping rules may be provided for different runtime environmentplatforms.

Methods and systems consistent with the subject matter described hereinprovide and use interfaces 320 derived from the business object model318 suitable for use with more than one business area, for exampledifferent departments within a company such as finance, or marketing.Also, they are suitable across industries and across businesses.Interfaces 320 are used during an end-to-end business transaction totransfer business process information in an application-independentmanner. For example the interfaces can be used for fulfilling a salesorder.

1. Message Overview

To perform an end-to-end business transaction, consistent interfaces areused to create business documents that are sent within messages betweenheterogeneous programs or modules.

a) Message Categories

As depicted in FIG. 6, the communication between a sender 602 and arecipient 604 can be broken down into basic categories that describe thetype of the information exchanged and simultaneously suggest theanticipated reaction of the recipient 604. A message category is ageneral business classification for the messages. Communication issender-driven. In other words, the meaning of the message categories isestablished or formulated from the perspective of the sender 602. Themessage categories include information 606, notification 608, query 610,response 612, request 614, and confirmation 616.

(1) Information

Information 606 is a message sent from a sender 602 to a recipient 604concerning a condition or a statement of affairs. No reply toinformation is expected. Information 606 is sent to make businesspartners or business applications aware of a situation. Information 606is not compiled to be application-specific. Examples of “information”are an announcement, advertising, a report, planning information, and amessage to the business warehouse.

(2) Notification

A notification 608 is a notice or message that is geared to a service. Asender 602 sends the notification 608 to a recipient 604. No reply isexpected for a notification. For example, a billing notification relatesto the preparation of an invoice while a dispatched deliverynotification relates to preparation for receipt of goods.

(3) Query

A query 610 is a question from a sender 602 to a recipient 604 to whicha response 612 is expected. A query 610 implies no assurance orobligation on the part of the sender 602. Examples of a query 610 arewhether space is available on a specific flight or whether a specificproduct is available. These queries do not express the desire forreserving the flight or purchasing the product.

(4) Response

A response 612 is a reply to a query 610. The recipient 604 sends theresponse 612 to the sender 602. A response 612 generally implies noassurance or obligation on the part of the recipient 604. The sender 602is not expected to reply. Instead, the process is concluded with theresponse 612. Depending on the business scenario, a response 612 alsomay include a commitment, i.e., an assurance or obligation on the partof the recipient 604. Examples of responses 612 are a response statingthat space is available on a specific flight or that a specific productis available. With these responses, no reservation was made.

(5) Request

A request 614 is a binding requisition or requirement from a sender 602to a recipient 604. Depending on the business scenario, the recipient604 can respond to a request 614 with a confirmation 616. The request614 is binding on the sender 602. In making the request 614, the sender602 assumes, for example, an obligation to accept the services renderedin the request 614 under the reported conditions. Examples of a request614 are a parking ticket, a purchase order, an order for delivery and ajob application.

(6) Confirmation

A confirmation 616 is a binding reply that is generally made to arequest 614. The recipient 604 sends the confirmation 616 to the sender602. The information indicated in a confirmation 616, such as deadlines,products, quantities and prices, can deviate from the information of thepreceding request 614. A request 614 and confirmation 616 may be used innegotiating processes. A negotiating process can consist of a series ofseveral request 614 and confirmation 616 messages. The confirmation 616is binding on the recipient 604. For example, 100 units of X may beordered in a purchase order request; however, only the delivery of 80units is confirmed in the associated purchase order confirmation.

b) Message Choreography

A message choreography is a template that specifies the sequence ofmessages between business entities during a given transaction. Thesequence with the messages contained in it describes in general themessage “lifecycle” as it proceeds between the business entities. Ifmessages from a choreography are used in a business transaction, theyappear in the transaction in the sequence determined by thechoreography. This illustrates the template character of a choreography,i.e., during an actual transaction, it is not necessary for all messagesof the choreography to appear. Those messages that are contained in thetransaction, however, follow the sequence within the choreography. Abusiness transaction is thus a derivation of a message choreography. Thechoreography makes it possible to determine the structure of theindividual message types more precisely and distinguish them from oneanother.

2. Components of the Business Object Model

The overall structure of the business object model ensures theconsistency of the interfaces that are derived from the business objectmodel. The derivation ensures that the same business-related subjectmatter or concept is represented and structured in the same way in allinterfaces.

The business object model defines the business-related concepts at acentral location for a number of business transactions. In other words,it reflects the decisions made about modeling the business entities ofthe real world acting in business transactions across industries andbusiness areas. The business object model is defined by the businessobjects and their relationship to each other (the overall netstructure).

Each business object is generally a capsule with an internalhierarchical structure, behavior offered by its operations, andintegrity constraints. Business objects are semantically disjoint, i.e.,the same business information is represented once. In the businessobject model, the business objects are arranged in an orderingframework. From left to right, they are arranged according to theirexistence dependency to each other. For example, the customizingelements may be arranged on the left side of the business object model,the strategic elements may be arranged in the center of the businessobject model, and the operative elements may be arranged on the rightside of the business object model. Similarly, the business objects arearranged from the top to the bottom based on defined order of thebusiness areas, e.g., finance could be arranged at the top of thebusiness object model with CRM below finance and SRM below CRM.

To ensure the consistency of interfaces, the business object model maybe built using standardized data types as well as packages to grouprelated elements together, and package templates and entity templates tospecify the arrangement of packages and entities within the structure.

a) Data Types

Data types are used to type object entities and interfaces with astructure. This typing can include business semantic. Such data typesmay include those generally described at pages 96 through 1642 (whichare incorporated by reference herein) of U.S. patent application Ser.No. 11/803,178, filed on May 11, 2007 and entitled “Consistent Set OfInterfaces Derived From A Business Object Model”. For example, the datatype BusinessTransactionDocumentID is a unique identifier for a documentin a business transaction. Also, as an example, Data typeBusinessTransactionDocumentParty contains the information that isexchanged in business documents about a party involved in a businesstransaction, and includes the party's identity, the party's address, theparty's contact person and the contact person's address.BusinessTransactionDocumentParty also includes the role of the party,e.g., a buyer, seller, product recipient, or vendor.

The data types are based on Core Component Types (“CCTs”), whichthemselves are based on the World Wide Web Consortium (“W3C”) datatypes. “Global” data types represent a business situation that isdescribed by a fixed structure. Global data types include bothcontext-neutral generic data types (“GDTs”) and context-based contextdata types (“CDTs”). GDTs contain business semantics, but areapplication-neutral, i.e., without context. CDTs, on the other hand, arebased on GDTs and form either a use-specific view of the GDTs, or acontext-specific assembly of GDTs or CDTs. A message is typicallyconstructed with reference to a use and is thus a use-specific assemblyof GDTs and CDTs. The data types can be aggregated to complex datatypes.

To achieve a harmonization across business objects and interfaces, thesame subject matter is typed with the same data type. For example, thedata type “GeoCoordinates” is built using the data type “Measure” sothat the measures in a GeoCoordinate (i.e., the latitude measure and thelongitude measure) are represented the same as other “Measures” thatappear in the business object model.

b) Entities

Entities are discrete business elements that are used during a businesstransaction. Entities are not to be confused with business entities orthe components that interact to perform a transaction. Rather,“entities” are one of the layers of the business object model and theinterfaces. For example, a Catalogue entity is used in a CataloguePublication Request and a Purchase Order is used in a Purchase OrderRequest. These entities are created using the data types defined aboveto ensure the consistent representation of data throughout the entities.

c) Packages

Packages group the entities in the business object model and theresulting interfaces into groups of semantically associated information.Packages also may include “sub”-packages, i.e., the packages may benested.

Packages may group elements together based on different factors, such aselements that occur together as a rule with regard to a business-relatedaspect. For example, as depicted in FIG. 7, in a Purchase Order,different information regarding the purchase order, such as the type ofpayment 702, and payment card 704, are grouped together via thePaymentInformation package 700.

Packages also may combine different components that result in a newobject. For example, as depicted in FIG. 8, the components wheels 804,motor 806, and doors 808 are combined to form a composition “Car” 802.The “Car” package 800 includes the wheels, motor and doors as well asthe composition “Car.”

Another grouping within a package may be subtypes within a type. Inthese packages, the components are specialized forms of a genericpackage. For example, as depicted in FIG. 9, the components Car 904,Boat 906, and Truck 908 can be generalized by the generic term Vehicle902 in Vehicle package 900. Vehicle in this case is the generic package910, while Car 912, Boat 914, and Truck 916 are the specializations 918of the generalized vehicle 910.

Packages also may be used to represent hierarchy levels. For example, asdepicted in FIG. 10, the Item Package 1000 includes Item 1002 withsubitem xxx 1004, subitem yyy 1006, and subitem zzz 1008.

Packages can be represented in the XML schema as a comment. Oneadvantage of this grouping is that the document structure is easier toread and is more understandable. The names of these packages areassigned by including the object name in brackets with the suffix“Package.” For example, as depicted in FIG. 11, Party package 1100 isenclosed by

<PartyPackage> 1102 and </PartyPackage> 1104. Party package 1100illustratively includes a Buyer Party 1106, identified by <BuyerParty>1108 and </BuyerParty> 1110, and a Seller Party 1112, identified by<SellerParty> 1114 and </SellerParty>, etc.

d) Relationships

Relationships describe the interdependencies of the entities in thebusiness object model, and are thus an integral part of the businessobject model.

(1) Cardinality of Relationships

FIG. 12 depicts a graphical representation of the cardinalities betweentwo entities. The cardinality between a first entity and a second entityidentifies the number of second entities that could possibly exist foreach first entity. Thus, a 1:c cardinality 1200 between entities A 1202and X 1204 indicates that for each entity A 1202, there is either one orzero 1206 entity X 1204. A 1:1 cardinality 1208 between entities A 1210and X 1212 indicates that for each entity A 1210, there is exactly one1214 entity X 1212. A 1:n cardinality 1216 between entities A 1218 and X1220 indicates that for each entity A 1218, there are one or more 1222entity Xs 1220. A 1:cn cardinality 1224 between entities A 1226 and X1228 indicates that for each entity A 1226, there are any number 1230 ofentity Xs 1228 (i.e., 0 through n Xs for each A).

(2) Types of Relationships

(a) Composition

A composition or hierarchical relationship type is a strong whole-partrelationship which is used to describe the structure within an object.The parts, or dependent entities, represent a semantic refinement orpartition of the whole, or less dependent entity. For example, asdepicted in FIG. 13, the components 1302, wheels 1304, and doors 1306may be combined to form the composite 1300 “Car” 1308 using thecomposition 1310. FIG. 14 depicts a graphical representation of thecomposition 1410 between composite Car 1408 and components wheel 1404and door 1406.

(b) Aggregation

An aggregation or an aggregating relationship type is a weak whole-partrelationship between two objects. The dependent object is created by thecombination of one or several less dependent objects. For example, asdepicted in FIG. 15, the properties of a competitor product 1500 aredetermined by a product 1502 and a competitor 1504. A hierarchicalrelationship 1506 exists between the product 1502 and the competitorproduct 1500 because the competitor product 1500 is a component of theproduct 1502. Therefore, the values of the attributes of the competitorproduct 1500 are determined by the product 1502. An aggregatingrelationship 1508 exists between the competitor 1504 and the competitorproduct 1500 because the competitor product 1500 is differentiated bythe competitor 1504. Therefore the values of the attributes of thecompetitor product 1500 are determined by the competitor 1504.

(c) Association

An association or a referential relationship type describes arelationship between two objects in which the dependent object refers tothe less dependent object. For example, as depicted in FIG. 16, a person1600 has a nationality, and thus, has a reference to its country 1602 oforigin. There is an association 1604 between the country 1602 and theperson 1600. The values of the attributes of the person 1600 are notdetermined by the country 1602.

(3) Specialization

Entity types may be divided into subtypes based on characteristics ofthe entity types. For example, FIG. 17 depicts an entity type “vehicle”1700 specialized 1702 into subtypes “truck” 1704, “car” 1706, and “ship”1708. These subtypes represent different aspects or the diversity of theentity type.

Subtypes may be defined based on related attributes. For example,although ships and cars are both vehicles, ships have an attribute,“draft,” that is not found in cars. Subtypes also may be defined basedon certain methods that can be applied to entities of this subtype andthat modify such entities. For example, “drop anchor” can be applied toships. If outgoing relationships to a specific object are restricted toa subset, then a subtype can be defined which reflects this subset.

As depicted in FIG. 18, specializations may further be characterized ascomplete specializations 1800 or incomplete specializations 1802. Thereis a complete specialization 1800 where each entity of the generalizedtype belongs to at least one subtype. With an incomplete specialization1802, there is at least one entity that does not belong to a subtype.Specializations also may be disjoint 1804 or nondisjoint 1806. In adisjoint specialization 1804, each entity of the generalized typebelongs to a maximum of one subtype. With a nondisjoint specialization1806, one entity may belong to more than one subtype. As depicted inFIG. 18, four specialization categories result from the combination ofthe specialization characteristics.

e) Structural Patterns

(1) Item

An item is an entity type which groups together features of anotherentity type. Thus, the features for the entity type chart of accountsare grouped together to form the entity type chart of accounts item. Forexample, a chart of accounts item is a category of values or value flowsthat can be recorded or represented in amounts of money in accounting,while a chart of accounts is a superordinate list of categories ofvalues or value flows that is defined in accounting.

The cardinality between an entity type and its item is often either 1:nor 1:cn. For example, in the case of the entity type chart of accounts,there is a hierarchical relationship of the cardinality 1:n with theentity type chart of accounts item since a chart of accounts has atleast one item in all cases.

(2) Hierarchy

A hierarchy describes the assignment of subordinate entities tosuperordinate entities and vice versa, where several entities of thesame type are subordinate entities that have, at most, one directlysuperordinate entity. For example, in the hierarchy depicted in FIG. 19,entity B 1902 is subordinate to entity A 1900, resulting in therelationship (A,B) 1912. Similarly, entity C 1904 is subordinate toentity A 1900, resulting in the relationship (A,C) 1914. Entity D 1906and entity E 1908 are subordinate to entity B 1902, resulting in therelationships (B,D) 1916 and (B,E) 1918, respectively. Entity F 1910 issubordinate to entity C 1904, resulting in the relationship (C,F) 1920.

Because each entity has at most one superordinate entity, thecardinality between a subordinate entity and its superordinate entity is1:c. Similarly, each entity may have 0, 1 or many subordinate entities.Thus, the cardinality between a superordinate entity and its subordinateentity is 1:cn. FIG. 20 depicts a graphical representation of a ClosingReport Structure Item hierarchy 2000 for a Closing Report Structure Item2002. The hierarchy illustrates the 1:c cardinality 2004 between asubordinate entity and its superordinate entity, and the 1:cncardinality 2006 between a superordinate entity and its subordinateentity.

3. Creation of the Business Object Model

FIGS. 21A-B depict the steps performed using methods and systemsconsistent with the subject matter described herein to create a businessobject model. Although some steps are described as being performed by acomputer, these steps may alternatively be performed manually, orcomputer-assisted, or any combination thereof. Likewise, although somesteps are described as being performed by a computer, these steps mayalso be computer-assisted, or performed manually, or any combinationthereof.

As discussed above, the designers create message choreographies thatspecify the sequence of messages between business entities during atransaction. After identifying the messages, the developers identify thefields contained in one of the messages (step 2100, FIG. 21A). Thedesigners then determine whether each field relates to administrativedata or is part of the object (step 2102). Thus, the first eleven fieldsidentified below in the left column are related to administrative data,while the remaining fields are part of the object.

MessageID Admin ReferenceID CreationDate SenderID AdditionalSenderIDContactPersonID SenderAddress RecipientID AdditionalRecipientIDContactPersonID RecipientAddress ID MainObject AdditionalID PostingDateLastChangeDate AcceptanceStatus Note CompleteTransmissionIndicator BuyerBuyerOrganisationName PersonName FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBoxPostalCode CompanyPostalCode CityNameDistrictName POBoxID POBoxIndicator POBoxCountryCode POBoxRegionCodePOBoxCityName StreetName HouseID BuildingID FloorID RoomID CareOfNameAddressDescription Telefonnumber MobileNumber Facsimile Email SellerSellerAddress Location LocationType DeliveryItemGroupID DeliveryPriorityDeliveryCondition TransferLocation NumberofPartialDeliveryQuantityTolerance MaximumLeadTime TransportServiceLevelTranportCondition TransportDescription CashDiscountTerms PaymentFormPaymentCardID PaymentCardReferenceID SequenceID Holder ExpirationDateAttachmentID AttachmentFilename DescriptionofMessageConfirmationDescriptionofMessage FollowUpActivity ItemID ParentItemIDHierarchyType ProductID ProductType ProductNote ProductCategoryID AmountBaseQuantity ConfirmedAmount ConfirmedBaseQuantity ItemBuyerItemBuyerOrganisationName PersonName FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBoxPostalCode CompanyPostalCode CityNameDistrictName POBoxID POBoxIndicator POBoxCountryCode POBoxRegionCodePOBoxCityName StreetName HouseID BuildingID FloorID RoomID CareOfNameAddressDescription Telefonnumber MobilNumber Facsimile Email ItemSellerItemSellerAddress ItemLocation ItemLocationType ItemDeliveryItemGroupIDItemDeliveryPriority ItemDeliveryCondition ItemTransferLocationItemNumberofPartialDelivery ItemQuantityTolerance ItemMaximumLeadTimeItemTransportServiceLevel ItemTranportCondition ItemTransportDescriptionContractReference QuoteReference CatalogueReference ItemAttachmentIDItemAttachmentFilename ItemDescription ScheduleLineID DeliveryPeriodQuantity ConfirmedScheduleLineID ConfirmedDeliveryPeriodConfirmedQuantity

Next, the designers determine the proper name for the object accordingto the ISO 11179 naming standards (step 2104). In the example above, theproper name for the “Main Object” is “Purchase Order.” After naming theobject, the system that is creating the business object model determineswhether the object already exists in the business object model (step2106). If the object already exists, the system integrates newattributes from the message into the existing object (step 2108), andthe process is complete.

If at step 2106 the system determines that the object does not exist inthe business object model, the designers model the internal objectstructure (step 2110). To model the internal structure, the designersdefine the components. For the above example, the designers may definethe components identified below.

ID Pur- AdditionalID chase- PostingDate Order LastChangeDateAcceptanceStatus Note CompleteTransmission Indicator Buyer BuyerBuyerOrganisationName PersonName FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBoxPostalCode CompanyPostalCode CityNameDistrictName POBoxID POBoxIndicator POBoxCountryCode POBoxRegionCodePOBoxCityName StreetName HouseID BuildingID FloorID RoomID CareOfNameAddressDescription Telefonnumber MobileNumber Facsimile Email SellerSeller SellerAddress Location Location LocationType DeliveryItemGroupIDDeliveryTerms DeliveryPriority DeliveryCondition TransferLocationNumberofPartialDelivery QuantityTolerance MaximumLeadTimeTransportServiceLevel TranportCondition TransportDescriptionCashDiscountTerms PaymentForm Payment PaymentCardIDPaymentCardReferenceID SequenceID Holder ExpirationDate AttachmentIDAttachmentFilename DescriptionofMessage ConfirmationDescriptionofMessage FollowUpActivity ItemID PurchaseOrder- ParentItemID ItemHierarchyType ProductID Product ProductType ProductNoteProductCategoryID ProductCategory Amount BaseQuantity ConfirmedAmountConfirmedBaseQuantity ItemBuyer Buyer ItemBuyerOrganisation NamePersonName FunctionalTitle DepartmentName CountryCode StreetPostalCodePOBoxPostalCode CompanyPostalCode CityName DistrictName POBoxIDPOBoxIndicator POBoxCountryCode POBoxRegionCode POBoxCityName StreetNameHouseID BuildingID FloorID RoomID CareOfName AddressDescriptionTelefonnumber MobilNumber Facsimile Email ItemSeller SellerItemSellerAddress ItemLocation Location ItemLocationTypeItemDeliveryItemGroupID ItemDeliveryPriority ItemDeliveryConditionItemTransferLocation ItemNumberofPartial Delivery ItemQuantityToleranceItemMaximumLeadTime ItemTransportServiceLevel ItemTranportConditionItemTransportDescription ContractReference Contract QuoteReference QuoteCatalogueReference Catalogue ItemAttachmentID ItemAttachmentFilenameItemDescription ScheduleLineID DeliveryPeriod QuantityConfirmedScheduleLineID ConfirmedDeliveryPeriod ConfirmedQuantity

During the step of modeling the internal structure, the designers alsomodel the complete internal structure by identifying the compositions ofthe components and the corresponding cardinalities, as shown below.

PurchaseOrder 1 Buyer 0 . . . 1 Address 0 . . . 1 ContactPerson 0 . . .1 Address 0 . . . 1 Seller 0 . . . 1 Location 0 . . . 1 Address 0 . . .1 DeliveryTerms 0 . . . 1 Incoterms 0 . . . 1 PartialDelivery 0 . . . 1QuantityTolerance 0 . . . 1 Transport 0 . . . 1 CashDiscount 0 . . . 1Terms MaximumCashDiscount 0 . . . 1 NormalCashDiscount 0 . . . 1PaymentForm 0 . . . 1 PaymentCard 0 . . . 1 Attachment 0 . . . nDescription 0 . . . 1 Confirmation 0 . . . 1 Description Item 0 . . . nHierarchyRelationship 0 . . . 1 Product 0 . . . 1 ProductCategory 0 . .. 1 Price 0 . . . 1 NetunitPrice 0 . . . 1 ConfirmedPrice 0 . . . 1NetunitPrice 0 . . . 1 Buyer 0 . . . 1 Seller 0 . . . 1 Location 0 . . .1 DeliveryTerms 0 . . . 1 Attachment 0 . . . n Description 0 . . . 1ConfirmationDescription 0 . . . 1 ScheduleLine 0 . . . n DeliveryPeriod1 ConfirmedScheduleLine 0 . . . n

After modeling the internal object structure, the developers identifythe subtypes and generalizations for all objects and components (step2112). For example, the Purchase Order may have subtypes Purchase OrderUpdate, Purchase Order Cancellation and Purchase Order Information.Purchase Order Update may include Purchase Order Request, Purchase OrderChange, and Purchase Order Confirmation. Moreover, Party may beidentified as the generalization of Buyer and Seller. The subtypes andgeneralizations for the above example are shown below.

Purchase- 1 Order PurchaseOrder Update PurchaseOrderRequestPurchaseOrderChange PurchaseOrder- Confirmation PurchaseOrder-Cancellation PurchaseOrder- Information Party BuyerParty 0 . . . 1Address 0 . . . 1 ContactPerson 0 . . . 1 Address 0 . . . 1 SellerParty0 . . . 1 Location ShipToLocation 0 . . . 1 Address 0 . . . 1ShipFromLocation 0 . . . 1 Address 0 . . . 1 DeliveryTerms 0 . . . 1Incoterms 0 . . . 1 PartialDelivery 0 . . . 1 QuantityTolerance 0 . . .1 Transport 0 . . . 1 CashDiscount- 0 . . . 1 Terms MaximumCashDiscount0 . . . 1 NormalCashDiscount 0 . . . 1 PaymentForm 0 . . . 1 PaymentCard0 . . . 1 Attachment 0 . . . n Description 0 . . . 1 Confirmation- 0 . .. 1 Description Item 0 . . . n HierarchyRelationship 0 . . . 1 Product 0. . . 1 ProductCategory 0 . . . 1 Price 0 . . . 1 NetunitPrice 0 . . . 1ConfirmedPrice 0 . . . 1 NetunitPrice 0 . . . 1 Party BuyerParty 0 . . .1 SellerParty 0 . . . 1 Location ShipTo 0 . . . 1 Location ShipFrom 0 .. . 1 Location DeliveryTerms 0 . . . 1 Attachment 0 . . . n Description0 . . . 1 Confirmation- 0 . . . 1 Description ScheduleLine 0 . . . nDelivery 1 Period ConfirmedScheduleLine 0 . . . n

After identifying the subtypes and generalizations, the developersassign the attributes to these components (step 2114). The attributesfor a portion of the components are shown below.

Purchase- 1 Order ID 1 SellerID 0 . . . 1 BuyerPosting- 0 . . . 1DateTime BuyerLast- 0 . . . 1 ChangeDate- Time SellerPosting- 0 . . . 1DateTime SellerLast- 0 . . . 1 ChangeDate- Time Acceptance- 0 . . . 1StatusCode Note 0 . . . 1 ItemList- 0 . . . 1 Complete- Transmission-Indicator BuyerParty 0 . . . 1 StandardID 0 . . . n BuyerID 0 . . . 1SellerID 0 . . . 1 Address 0 . . . 1 ContactPerson 0 . . . 1 BuyerID 0 .. . 1 SellerID 0 . . . 1 Address 0 . . . 1 SellerParty 0 . . . 1Product- 0 . . . 1 RecipientParty VendorParty 0 . . . 1 Manufacturer- 0. . . 1 Party BillToParty 0 . . . 1 PayerParty 0 . . . 1 CarrierParty 0. . . 1 ShipTo- 0 . . . 1 Location StandardID 0 . . . n BuyerID 0 . . .1 SellerID 0 . . . 1 Address 0 . . . 1 ShipFrom- 0 . . . 1 Location

The system then determines whether the component is one of the objectnodes in the business object model (step 2116, FIG. 21B). If the systemdetermines that the component is one of the object nodes in the businessobject model, the system integrates a reference to the correspondingobject node from the business object model into the object (step 2118).In the above example, the system integrates the reference to the Buyerparty represented by an ID and the reference to the ShipToLocationrepresented by an into the object, as shown below. The attributes thatwere formerly located in the PurchaseOrder object are now assigned tothe new found object party. Thus, the attributes are removed from thePurchaseOrder object.

PurchaseOrder ID SellerID BuyerPostingDateTime BuyerLastChangeDateTimeSellerPostingDateTime SellerLastChangeDateTime AcceptanceStatusCode NoteItemListComplete TransmissionIndicator BuyerParty ID SellerPartyProductRecipientParty VendorParty ManufacturerParty BillToPartyPayerParty CarrierParty ShipToLocation ID ShipFromLocation

During the integration step, the designers classify the relationship(i.e., aggregation or association) between the object node and theobject being integrated into the business object model. The system alsointegrates the new attributes into the object node (step 2120). If atstep 2116, the system determines that the component is not in thebusiness object model, the system adds the component to the businessobject model (step 2122).

Regardless of whether the component was in the business object model atstep 2116, the next step in creating the business object model is to addthe integrity rules (step 2124). There are several levels of integrityrules and constraints which should be described. These levels includeconsistency rules between attributes, consistency rules betweencomponents, and consistency rules to other objects. Next, the designersdetermine the services offered, which can be accessed via interfaces(step 2126). The services offered in the example above includePurchaseOrderCreateRequest, PurchaseOrderCancellationRequest, andPurchaseOrderReleaseRequest. The system then receives an indication ofthe location for the object in the business object model (step 2128).After receiving the indication of the location, the system integratesthe object into the business object model (step 2130).

4. Structure of the Business Object Model

The business object model, which serves as the basis for the process ofgenerating consistent interfaces, includes the elements contained withinthe interfaces. These elements are arranged in a hierarchical structurewithin the business object model.

5. Interfaces Derived from Business Object Model

Interfaces are the starting point of the communication between twobusiness entities. The structure of each interface determines how onebusiness entity communicates with another business entity. The businessentities may act as a unified whole when, based on the businessscenario, the business entities know what an interface contains from abusiness perspective and how to fill the individual elements or fieldsof the interface. As illustrated in FIG. 27A, communication betweencomponents takes place via messages that contain business documents(e.g., business document 27002). The business document 27002 ensures aholistic business-related understanding for the recipient of themessage. The business documents are created and accepted or consumed byinterfaces, specifically by inbound and outbound interfaces. Theinterface structure and, hence, the structure of the business documentare derived by a mapping rule. This mapping rule is known as“hierarchization.” An interface structure thus has a hierarchicalstructure created based on the leading business object 27000. Theinterface represents a usage-specific, hierarchical view of theunderlying usage-neutral object model.

As illustrated in FIG. 27B, several business document objects 27006,27008, and 27010 as overlapping views may be derived for a given leadingobject 27004. Each business document object results from the objectmodel by hierarchization.

To illustrate the hierarchization process, FIG. 27C depicts an exampleof an object model 27012 (i.e., a portion of the business object model)that is used to derive a service operation signature (business documentobject structure). As depicted, leading object X 27014 in the objectmodel 27012 is integrated in a net of object A 27016, object B 27018,and object C 27020. Initially, the parts of the leading object 27014that are required for the business object document are adopted. In onevariation, all parts required for a business document object are adoptedfrom leading object 27014 (making such an operation a maximal serviceoperation). Based on these parts, the relationships to the superordinateobjects (i.e., objects A, B, and C from which object X depends) areinverted. In other words, these objects are adopted as dependent orsubordinate objects in the new business document object.

For example, object A 27016, object B 27018, and object C 27020 haveinformation that characterize object X. Because object A 27016, object B27018, and object C 27020 are superordinate to leading object X 27014,the dependencies of these relationships change so that object A 27016,object B 27018, and object C 27020 become dependent and subordinate toleading object X 27014. This procedure is known as “derivation of thebusiness document object by hierarchization.”

Business-related objects generally have an internal structure (parts).This structure can be complex and reflect the individual parts of anobject and their mutual dependency. When creating the operationsignature, the internal structure of an object is strictly hierarchized.Thus, dependent parts keep their dependency structure, and relationshipsbetween the parts within the object that do not represent thehierarchical structure are resolved by prioritizing one of therelationships.

Relationships of object X to external objects that are referenced andwhose information characterizes object X are added to the operationsignature. Such a structure can be quite complex (see, for example, FIG.27D). The cardinality to these referenced objects is adopted as 1:1 or1:C, respectively. By this, the direction of the dependency changes. Therequired parts of this referenced object are adopted identically, bothin their cardinality and in their dependency arrangement.

The newly created business document object contains all requiredinformation, including the incorporated master data information of thereferenced objects. As depicted in FIG. 27D, components Xi in leadingobject X 27022 are adopted directly. The relationship of object X 27022to object A 27024, object B 27028, and object C 27026 are inverted, andthe parts required by these objects are added as objects that dependfrom object X 27022. As depicted, all of object A 27024 is adopted. B3and B4 are adopted from object B 27028, but B1 is not adopted. Fromobject C 27026, C2 and C1 are adopted, but C3 is not adopted.

FIG. 27E depicts the business document object X 27030 created by thishierarchization process. As shown, the arrangement of the elementscorresponds to their dependency levels, which directly leads to acorresponding representation as an XML structure 27032.

The following provides certain rules that can be adopted singly or incombination with regard to the hierarchization process. A businessdocument object always refers to a leading business document object andis derived from this object. The name of the root entity in the businessdocument entity is the name of the business object or the name of aspecialization of the business object or the name of a service specificview onto the business object. The nodes and elements of the businessobject that are relevant (according to the semantics of the associatedmessage type) are contained as entities and elements in the businessdocument object.

The name of a business document entity is predefined by the name of thecorresponding business object node. The name of the superordinate entityis not repeated in the name of the business document entity. The “full”semantic name results from the concatenation of the entity names alongthe hierarchical structure of the business document object.

The structure of the business document object is, except for deviationsdue to hierarchization, the same as the structure of the businessobject. The cardinalities of the business document object nodes andelements are adopted identically or more restrictively to the businessdocument object. An object from which the leading business object isdependent can be adopted to the business document object. For thisarrangement, the relationship is inverted, and the object (or its parts,respectively) are hierarchically subordinated in the business documentobject.

Nodes in the business object representing generalized businessinformation can be adopted as explicit entities to the business documentobject (generally speaking, multiply TypeCodes out). When this adoptionoccurs, the entities are named according to their more specific semantic(name of TypeCode becomes prefix). Party nodes of the business objectare modeled as explicit entities for each party role in the businessdocument object. These nodes are given the name <Prefix><PartyRole>Party, for example, BuyerParty, ItemBuyerParty. BTDReference nodesare modeled as separate entities for each reference type in the businessdocument object. These nodes are given the name<Qualifier><BO><Node>Reference, for example SalesOrderReference,OriginSalesOrderReference, SalesOrderItemReference. A product node inthe business object comprises all of the information on the Product,ProductCategory, and Batch. This information is modeled in the businessdocument object as explicit entities for Product, ProductCategory, andBatch.

Entities which are connected by a 1:1 relationship as a result ofhierarchization can be combined to a single entity, if they aresemantically equivalent. Such a combination can often occurs if a nodein the business document object that results from an assignment node isremoved because it does not have any elements.

The message type structure is typed with data types. Elements are typedby GDTs according to their business objects. Aggregated levels are typedwith message type specific data types (Intermediate Data Types), withtheir names being built according to the corresponding paths in themessage type structure. The whole message type structured is typed by amessage data type with its name being built according to the root entitywith the suffix “Message”. For the message type, the message category(e.g., information, notification, query, response, request,confirmation, etc.) is specified according to the suited transactioncommunication pattern.

In one variation, the derivation by hierarchization can be initiated byspecifying a leading business object and a desired view relevant for aselected service operation. This view determines the business documentobject. The leading business object can be the source object, the targetobject, or a third object. Thereafter, the parts of the business objectrequired for the view are determined. The parts are connected to theroot node via a valid path along the hierarchy. Thereafter, one or moreindependent objects (object parts, respectively) referenced by theleading object which are relevant for the service may be determined(provided that a relationship exists between the leading object and theone or more independent objects).

Once the selection is finalized, relevant nodes of the leading objectnode that are structurally identical to the message type structure canthen be adopted. If nodes are adopted from independent objects or objectparts, the relationships to such independent objects or object parts areinverted. Linearization can occur such that a business object nodecontaining certain TypeCodes is represented in the message typestructure by explicit entities (an entity for each value of theTypeCode). The structure can be reduced by checking all 1:1cardinalities in the message type structure. Entities can be combined ifthey are semantically equivalent, one of the entities carries noelements, or an entity solely results from an n:m assignment in thebusiness object.

After the hierarchization is completed, information regardingtransmission of the business document object (e.g.,CompleteTransmissionIndicator, ActionCodes, message category, etc.) canbe added. A standardized message header can be added to the message typestructure and the message structure can be typed. Additionally, themessage category for the message type can be designated.

Invoice Request and Invoice Confirmation are examples of interfaces.These invoice interfaces are used to exchange invoices and invoiceconfirmations between an invoicing party and an invoice recipient (suchas between a seller and a buyer) in a B2B process. Companies can createinvoices in electronic as well as in paper form. Traditional methods ofcommunication, such as mail or fax, for invoicing are cost intensive,prone to error, and relatively slow, since the data is recordedmanually. Electronic communication eliminates such problems. Themotivating business scenarios for the Invoice Request and InvoiceConfirmation interfaces are the Procure to Stock (PTS) and Sell fromStock (SFS) scenarios. In the PTS scenario, the parties use invoiceinterfaces to purchase and settle goods. In the SFS scenario, theparties use invoice interfaces to sell and invoice goods. The invoiceinterfaces directly integrate the applications implementing them andalso form the basis for mapping data to widely-used XML standard formatssuch as RosettaNet, PIDX, xCBL, and CIDX.

The invoicing party may use two different messages to map a B2Binvoicing process: (1) the invoicing party sends the message typeInvoiceRequest to the invoice recipient to start a new invoicingprocess; and (2) the invoice recipient sends the message typeInvoiceConfirmation to the invoicing party to confirm or reject anentire invoice or to temporarily assign it the status “pending.”

An InvoiceRequest is a legally binding notification of claims orliabilities for delivered goods and rendered services—usually, a paymentrequest for the particular goods and services. The message typeInvoiceRequest is based on the message data type InvoiceMessage. TheInvoiceRequest message (as defined) transfers invoices in the broadersense. This includes the specific invoice (request to settle aliability), the debit memo, and the credit memo.

InvoiceConfirmation is a response sent by the recipient to the invoicingparty confirming or rejecting the entire invoice received or statingthat it has been assigned temporarily the status “pending.” The messagetype InvoiceConfirmation is based on the message data typeInvoiceMessage. An InvoiceConfirmation is not mandatory in a B2Binvoicing process, however, it automates collaborative processes anddispute management.

Usually, the invoice is created after it has been confirmed that thegoods were delivered or the service was provided. The invoicing party(such as the seller) starts the invoicing process by sending anInvoiceRequest message. Upon receiving the InvoiceRequest message, theinvoice recipient (for instance, the buyer) can use theInvoiceConfirmation message to completely accept or reject the invoicereceived or to temporarily assign it the status “pending.” TheInvoiceConfirmation is not a negotiation tool (as is the case in ordermanagement), since the options available are either to accept or rejectthe entire invoice. The invoice data in the InvoiceConfirmation messagemerely confirms that the invoice has been forwarded correctly and doesnot communicate any desired changes to the invoice. Therefore, theInvoiceConfirmation includes the precise invoice data that the invoicerecipient received and checked. If the invoice recipient rejects aninvoice, the invoicing party can send a new invoice after checking thereason for rejection (AcceptanceStatus and ConfirmationDescription atInvoice and InvoiceItem level). If the invoice recipient does notrespond, the invoice is generally regarded as being accepted and theinvoicing party can expect payment.

FIGS. 22A-F depict a flow diagram of the steps performed by methods andsystems consistent with the subject matter described herein to generatean interface from the business object model. Although described as beingperformed by a computer, these steps may alternatively be performedmanually, or using any combination thereof. The process begins when thesystem receives an indication of a package template from the designer,i.e., the designer provides a package template to the system (step2200).

Package templates specify the arrangement of packages within a businesstransaction document. Package templates are used to define the overallstructure of the messages sent between business entities. Methods andsystems consistent with the subject matter described herein use packagetemplates in conjunction with the business object model to derive theinterfaces.

The system also receives an indication of the message type from thedesigner (step 2202). The system selects a package from the packagetemplate (step 2204), and receives an indication from the designerwhether the package is required for the interface (step 2206). If thepackage is not required for the interface, the system removes thepackage from the package template (step 2208). The system then continuesthis analysis for the remaining packages within the package template(step 2210).

If, at step 2206, the package is required for the interface, the systemcopies the entity template from the package in the business object modelinto the package in the package template (step 2212, FIG. 22B). Thesystem determines whether there is a specialization in the entitytemplate (step 2214). If the system determines that there is aspecialization in the entity template, the system selects a subtype forthe specialization (step 2216). The system may either select the subtypefor the specialization based on the message type, or it may receive thisinformation from the designer. The system then determines whether thereare any other specializations in the entity template (step 2214). Whenthe system determines that there are no specializations in the entitytemplate, the system continues this analysis for the remaining packageswithin the package template (step 2210, FIG. 22A).

At step 2210, after the system completes its analysis for the packageswithin the package template, the system selects one of the packagesremaining in the package template (step 2218, FIG. 22C), and selects anentity from the package (step 2220). The system receives an indicationfrom the designer whether the entity is required for the interface (step2222). If the entity is not required for the interface, the systemremoves the entity from the package template (step 2224). The systemthen continues this analysis for the remaining entities within thepackage (step 2226), and for the remaining packages within the packagetemplate (step 2228).

If, at step 2222, the entity is required for the interface, the systemretrieves the cardinality between a superordinate entity and the entityfrom the business object model (step 2230, FIG. 22D). The system alsoreceives an indication of the cardinality between the superordinateentity and the entity from the designer (step 2232). The system thendetermines whether the received cardinality is a subset of the businessobject model cardinality (step 2234). If the received cardinality is nota subset of the business object model cardinality, the system sends anerror message to the designer (step 2236). If the received cardinalityis a subset of the business object model cardinality, the system assignsthe received cardinality as the cardinality between the superordinateentity and the entity (step 2238). The system then continues thisanalysis for the remaining entities within the package (step 2226, FIG.22C), and for the remaining packages within the package template (step2228).

The system then selects a leading object from the package template (step2240, FIG. 22E). The system determines whether there is an entitysuperordinate to the leading object (step 2242). If the systemdetermines that there is an entity superordinate to the leading object,the system reverses the direction of the dependency (step 2244) andadjusts the cardinality between the leading object and the entity (step2246). The system performs this analysis for entities that aresuperordinate to the leading object (step 2242). If the systemdetermines that there are no entities superordinate to the leadingobject, the system identifies the leading object as analyzed (step2248).

The system then selects an entity that is subordinate to the leadingobject (step 2250, FIG. 22F). The system determines whether anynon-analyzed entities are superordinate to the selected entity (step2252). If a non-analyzed entity is superordinate to the selected entity,the system reverses the direction of the dependency (step 2254) andadjusts the cardinality between the selected entity and the non-analyzedentity (step 2256). The system performs this analysis for non-analyzedentities that are superordinate to the selected entity (step 2252). Ifthe system determines that there are no non-analyzed entitiessuperordinate to the selected entity, the system identifies the selectedentity as analyzed (step 2258), and continues this analysis for entitiesthat are subordinate to the leading object (step 2260). After thepackages have been analyzed, the system substitutes theBusinessTransactionDocument (“BTD”) in the package template with thename of the interface (step 2262). This includes the “BTD” in theBTDItem package and the “BTD” in the BTDItemScheduleLine package.

6. Use of an Interface

The XI stores the interfaces (as an interface type). At runtime, thesending party's program instantiates the interface to create a businessdocument, and sends the business document in a message to the recipient.The messages are preferably defined using XML. In the example depictedin FIG. 23, the Buyer 2300 uses an application 2306 in its system toinstantiate an interface 2308 and create an interface object or businessdocument object 2310. The Buyer's application 2306 uses data that is inthe sender's component-specific structure and fills the businessdocument object 2310 with the data. The Buyer's application 2306 thenadds message identification 2312 to the business document and places thebusiness document into a message 2302. The Buyer's application 2306sends the message 2302 to the Vendor 2304. The Vendor 2304 uses anapplication 2314 in its system to receive the message 2302 and store thebusiness document into its own memory. The Vendor's application 2314unpacks the message 2302 using the corresponding interface 2316 storedin its XI to obtain the relevant data from the interface object orbusiness document object 2318.

From the component's perspective, the interface is represented by aninterface proxy 2400, as depicted in FIG. 24. The proxies 2400 shieldthe components 2402 of the sender and recipient from the technicaldetails of sending messages 2404 via XI. In particular, as depicted inFIG. 25, at the sending end, the Buyer 2500 uses an application 2510 inits system to call an implemented method 2512, which generates theoutbound proxy 2506. The outbound proxy 2506 parses the internal datastructure of the components and converts them to the XML structure inaccordance with the business document object. The outbound proxy 2506packs the document into a message 2502. Transport, routing and mappingthe XML message to the recipient 28304 is done by the routing system(XI, modeling environment 516, etc.).

When the message arrives, the recipient's inbound proxy 2508 calls itscomponent-specific method 2514 for creating a document. The proxy 2508at the receiving end downloads the data and converts the XML structureinto the internal data structure of the recipient component 2504 forfurther processing.

As depicted in FIG. 26A, a message 2600 includes a message header 2602and a business document 2604. The message 2600 also may include anattachment 2606. For example, the sender may attach technical drawings,detailed specifications or pictures of a product to a purchase order forthe product. The business document 2604 includes a business documentmessage header 2608 and the business document object 2610. The businessdocument message header 2608 includes administrative data, such as themessage ID and a message description. As discussed above, the structure2612 of the business document object 2610 is derived from the businessobject model 2614. Thus, there is a strong correlation between thestructure of the business document object and the structure of thebusiness object model. The business document object 2610 forms the coreof the message 2600.

In collaborative processes as well as Q&A processes, messages shouldrefer to documents from previous messages. A simple business documentobject ID or object ID is insufficient to identify individual messagesuniquely because several versions of the same business document objectcan be sent during a transaction. A business document object ID with aversion number also is insufficient because the same version of abusiness document object can be sent several times. Thus, messagesrequire several identifiers during the course of a transaction.

As depicted in FIG. 26B, the message header 2618 in message 2616includes a technical ID (“ID4”) 2622 that identifies the address for acomputer to route the message. The sender's system manages the technicalID 2622.

The administrative information in the business document message header2624 of the payload or business document 2620 includes aBusinessDocumentMessageID (“ID3”) 2628. The business entity or component2632 of the business entity manages and sets theBusinessDocumentMessageID 2628. The business entity or component 2632also can refer to other business documents using theBusinessDocumentMessageID 2628. The receiving component 2632 requires noknowledge regarding the structure of this ID. TheBusinessDocumentMessageID 2628 is, as an ID, unique. Creation of amessage refers to a point in time. No versioning is typically expressedby the ID. Besides the BusinessDocumentMessageID 2628, there also is abusiness document object ID 2630, which may include versions.

The component 2632 also adds its own component object ID 2634 when thebusiness document object is stored in the component. The componentobject ID 2634 identifies the business document object when it is storedwithin the component. However, not all communication partners may beaware of the internal structure of the component object ID 2634. Somecomponents also may include a versioning in their ID 2634.

7. Use of Interfaces Across Industries

Methods and systems consistent with the subject matter described hereinprovide interfaces that may be used across different business areas fordifferent industries. Indeed, the interfaces derived using methods andsystems consistent with the subject matter described herein may bemapped onto the interfaces of different industry standards. Unlike theinterfaces provided by any given standard that do not include theinterfaces required by other standards, methods and systems consistentwith the subject matter described herein provide a set of consistentinterfaces that correspond to the interfaces provided by differentindustry standards. Due to the different fields provided by eachstandard, the interface from one standard does not easily map ontoanother standard. By comparison, to map onto the different industrystandards, the interfaces derived using methods and systems consistentwith the subject matter described herein include most of the fieldsprovided by the interfaces of different industry standards. Missingfields may easily be included into the business object model. Thus, byderivation, the interfaces can be extended consistently by these fields.Thus, methods and systems consistent with the subject matter describedherein provide consistent interfaces or services that can be used acrossdifferent industry standards.

For example, FIG. 28 illustrates an example method 2800 for serviceenabling. In this example, the enterprise services infrastructure mayoffer one common and standard-based service infrastructure. Further, onecentral enterprise services repository may support uniform servicedefinition, implementation and usage of services for user interface, andcross-application communication. In step 2801, a business object isdefined via a process component model in a process modeling phase. Next,in step 2802, the business object is designed within an enterpriseservices repository. For example, FIG. 29 provides a graphicalrepresentation of one of the business objects 2900. As shown, aninnermost layer or kernel 2901 of the business object may represent thebusiness object's inherent data. Inherent data may include, for example,an employee's name, age, status, position, address, etc. A second layer2902 may be considered the business object's logic. Thus, the layer 2902includes the rules for consistently embedding the business object in asystem environment as well as constraints defining values and domainsapplicable to the business object. For example, one such constraint maylimit sale of an item only to a customer with whom a company has abusiness relationship. A third layer 2903 includes validation optionsfor accessing the business object. For example, the third layer 2903defines the business object's interface that may be interfaced by otherbusiness objects or applications. A fourth layer 2904 is the accesslayer that defines technologies that may externally access the businessobject.

Accordingly, the third layer 2903 separates the inherent data of thefirst layer 2901 and the technologies used to access the inherent data.As a result of the described structure, the business object reveals onlyan interface that includes a set of clearly defined methods. Thus,applications access the business object via those defined methods. Anapplication wanting access to the business object and the dataassociated therewith usually includes the information or data to executethe clearly defined methods of the business object's interface. Suchclearly defined methods of the business object's interface represent thebusiness object's behavior. That is, when the methods are executed, themethods may change the business object's data. Therefore, an applicationmay utilize any business object by providing the information or datawithout having any concern for the details related to the internaloperation of the business object. Returning to method 2800, a serviceprovider class and data dictionary elements are generated within adevelopment environment at step 2803. In step 2804, the service providerclass is implemented within the development environment.

FIG. 30 illustrates an example method 3000 for a process agentframework. For example, the process agent framework may be the basicinfrastructure to integrate business processes located in differentdeployment units. It may support a loose coupling of these processes bymessage based integration. A process agent may encapsulate the processintegration logic and separate it from business logic of businessobjects. As shown in FIG. 30, an integration scenario and a processcomponent interaction model are defined during a process modeling phasein step 3001. In step 3002, required interface operations and processagents are identified during the process modeling phase also. Next, instep 3003, a service interface, service interface operations, and therelated process agent are created within an enterprise servicesrepository as defined in the process modeling phase. In step 3004, aproxy class for the service interface is generated. Next, in step 3005,a process agent class is created and the process agent is registered. Instep 3006, the agent class is implemented within a developmentenvironment.

FIG. 31 illustrates an example method 3100 for status and actionmanagement (S&AM). For example, status and action management maydescribe the life cycle of a business object (node) by defining actionsand statuses (as their result) of the business object (node), as wellas, the constraints that the statuses put on the actions. In step 3101,the status and action management schemas are modeled per a relevantbusiness object node within an enterprise services repository. In step3102, existing statuses and actions from the business object model areused or new statuses and actions are created. Next, in step 3103, theschemas are simulated to verify correctness and completeness. In step3104, missing actions, statuses, and derivations are created in thebusiness object model with the enterprise services repository.Continuing with method 3100, the statuses are related to correspondingelements in the node in step 3105. In step 3106, status code GDT's aregenerated, including constants and code list providers. Next, in step3107, a proxy class for a business object service provider is generatedand the proxy class S&AM schemas are imported. In step 3108, the serviceprovider is implemented and the status and action management runtimeinterface is called from the actions.

Regardless of the particular hardware or software architecture used, thedisclosed systems or software are generally capable of implementingbusiness objects and deriving (or otherwise utilizing) consistentinterfaces that are suitable for use across industries, acrossbusinesses, and across different departments within a business inaccordance with some or all of the following description. In short,system 100 contemplates using any appropriate combination andarrangement of logical elements to implement some or all of thedescribed functionality.

Moreover, the preceding flowcharts and accompanying descriptionillustrate example methods. The present services environmentcontemplates using or implementing any suitable technique for performingthese and other tasks. It will be understood that these methods are forillustration purposes only and that the described or similar techniquesmay be performed at any appropriate time, including concurrently,individually, or in combination. In addition, many of the steps in theseflowcharts may take place simultaneously and/or in different orders thanas shown. Moreover, the services environment may use methods withadditional steps, fewer steps, and/or different steps, so long as themethods remain appropriate.

FIGS. 32-1 through 32-3 collectively illustrate one example logicalconfiguration of an Opportunity Replication Request message 32000.Specifically, these figures depict the arrangement and hierarchy ofvarious components such as one or more levels of packages, entities, anddata types, shown here as 32002 through 32046. As described above,packages may be used to represent hierarchy levels, and different typesof cardinality relationships among entities can be represented usingdifferent arrowhead styles. Entities are discrete business elements thatare used during a business transaction. Data types are used to typeobject entities and interfaces with a structure. For example, theOpportunity Replication Request message 32000 includes, among otherthings, the Opportunity entity 32006. Accordingly, heterogeneousapplications may communicate using this consistent message configured assuch.

The message type Opportunity Replication Request is derived from thebusiness object Opportunity as a leading object together with itsoperation signature. The message type Opportunity Replication Request isa request to replicate opportunity data. The structure of the messagetype Opportunity Replication Request is determined by the message datatype OpportunityReplicationRequest. The message data typeOpportunityReplicationRequest includes the MessageHeader package and theOpportunity package. The package MessageHeader includes the sub-packagesParty and Business Scope and the entity MessageHeader. MessageHeader istyped by BusinessDocumentMessageHeader.

The package Opportunity includes the sub-packages Status, ProspectParty,CompetitorParty, SalesEmployeeParty, EmployeeResponsible,SalesUnitParty, Party, SalesCycle, SalesForecast,SalesAndServiceBusinessArea, BusinessTransactionDocumentReference,AttachmentFolder, TextCollection, and Item, and the entity Opportunity.

Opportunity includes the following non-node elements: ID,SystemAdministrativeData, ProcessingTypeCode, Name, PriorityCode,ProcessStatusValidSinceDate, GroupCode, OriginTypeCode,ResultReasonCode, and ChangeOrdinalNumberValue. ID may have amultiplicity of 1 and may be based on datatypeBGDT:BusinessTransactionDocumentID. SystemAdministrativeData may have amultiplicity of 0 . . . 1 and may be based on datatypeAGDT:USERACCOUNTBASED_SystemAdministrativeData. ProcessingTypeCode mayhave a multiplicity of 1 and may be based on datatypeBGDT:BusinessTransactionDocumentProcessingTypeCode. Name may have amultiplicity of 0 . . . 1 and may be based on datatypeCDT:EXTENDED_Name. PriorityCode may have a multiplicity of 0 . . . 1 andmay be based on datatype BGDT:PriorityCode. ProcessStatusValidSinceDatemay have a multiplicity of 1 and may be based on datatype CDT:Date.GroupCode may have a multiplicity of 0 . . . 1 and may be based ondatatype BGDT:OpportunityGroupCode. OriginTypeCode may have amultiplicity of 0 . . . 1 and may be based on datatypeBGDT:CustomerTransactionDocumentOriginTypeCode. ResultReasonCode mayhave a multiplicity of 0 . . . 1 and may be based on datatypeBGDT:CustomerTransactionDocumentResultReasonCode.ChangeOrdinalNumberValue may have a multiplicity of 0 . . . 1 and may bebased on datatype BGDT:OrdinalNumberValue_V1.

Opportunity includes the following node elements: Status, in a 1:1cardinality relationship; ProspectParty, in a 1:C cardinalityrelationship; CompetitorParty, in a 1:CN cardinality relationship;SalesEmployeeParty, in a 1:CN cardinality relationship;EmployeeResponsible, in a 1:C cardinality relationship; SalesUnitParty,in a 1:C cardinality relationship; Party, in a 1:CN cardinalityrelationship; SalesCycle, in a 1:C cardinality relationship;SalesForecast, in a 1:C cardinality relationship;SalesAndServiceBusinessArea, in a 1:C cardinality relationship;BusinessTransactionDocumentReference, in a 1:CN cardinalityrelationship; AttachmentFolder, in a 1:C cardinality relationship;TextCollection, in a 1:C cardinality relationship; and Item, in a 1:CNcardinality relationship.

The package OpportunityStatus includes the entity Status. Statusincludes the LifeCycleStatusCode non-node element, which may have amultiplicity of 0 . . . 1 and may be based on datatypeBGDT:OpportunityLifeCycleStatusCode.

The package OpportunityProspectParty includes the sub-packageContactParty and the entity ProspectParty. ProspectParty includes thefollowing non-node elements: PartyID, RecipientPartyID, and RoleCode.PartyID may have a multiplicity of 1 and may be based on datatypeBGDT:PartyID. RecipientPartyID may have a multiplicity of 0 . . . 1 andmay be based on datatype BGDT:PartyID. RoleCode may have a multiplicityof 0 . . . 1 and may be based on datatype BGDT:PartyRoleCode.ProspectParty includes the following node elements: ContactParty, in a1:CN cardinality relationship.

The package OpportunityProspectPartyContactParty includes the entityContactParty. ContactParty includes the following non-node elements:PartyID, RoleCode, RecipientPartyID, and MainIndicator. PartyID may havea multiplicity of 0 . . . 1 and may be based on datatype BGDT:PartyID.RoleCode may have a multiplicity of 0 . . . 1 and may be based ondatatype BGDT:PartyRoleCode. RecipientPartyID may have a multiplicity of0 . . . 1 and may be based on datatype BGDT:PartyID. MainIndicator mayhave a multiplicity of 0 . . . 1 and may be based on datatypeCDT:Indicator.

The package OpportunityCompetitorParty includes the entityCompetitorParty. CompetitorParty includes the following non-nodeelements: PartyID, RoleCode, RecipientPartyID, and MainIndicator.PartyID may have a multiplicity of 0 . . . 1 and may be based ondatatype BGDT:PartyID. RoleCode may have a multiplicity of 0 . . . 1 andmay be based on datatype BGDT:PartyRoleCode. RecipientPartyID may have amultiplicity of 0 . . . 1 and may be based on datatype BGDT:PartyID.MainIndicator may have a multiplicity of 0 . . . 1 and may be based ondatatype CDT:Indicator.

The package OpportunitySalesEmployeeParty includes the entitySalesEmployeeParty. SalesEmployeeParty includes the following non-nodeelements: PartyID, RecipientPartyID, and RoleCode. PartyID may have amultiplicity of 0 . . . 1 and may be based on datatype BGDT:PartyID.RecipientPartyID may have a multiplicity of 0 . . . 1 and may be basedon datatype BGDT:PartyID. RoleCode may have a multiplicity of 0 . . . 1and may be based on datatype BGDT:PartyRoleCode.

The package OpportunityEmployeeResponsible includes the entityEmployeeResponsible. EmployeeResponsible includes the following non-nodeelements: PartyID, RecipientPartyID, and RoleCode. PartyID may have amultiplicity of 0 . . . 1 and may be based on datatype BGDT:PartyID.RecipientPartyID may have a multiplicity of 0 . . . 1 and may be basedon datatype BGDT:PartyID. RoleCode may have a multiplicity of 0 . . . 1and may be based on datatype BGDT:PartyRoleCode.

The package OpportunitySalesUnitParty includes the entitySalesUnitParty. SalesUnitParty includes the following non-node elements:PartyID, RecipientPartyID, and RoleCode. PartyID may have a multiplicityof 0 . . . 1 and may be based on datatype BGDT:PartyID. RecipientPartyIDmay have a multiplicity of 0 . . . 1 and may be based on datatypeBGDT:PartyID. RoleCode may have a multiplicity of 0 . . . 1 and may bebased on datatype BGDT:PartyRoleCode.

The package OpportunityParty includes the sub-package ContactParty andthe entity Party. Party includes the following non-node elements:PartyID, RecipientPartyID, RoleCode, RoleCategoryCode, andMainIndicator. PartyID may have a multiplicity of 1 and may be based ondatatype BGDT:PartyID. RecipientPartyID may have a multiplicity of 0 . .. 1 and may be based on datatype BGDT:PartyID. RoleCode may have amultiplicity of 0 . . . 1 and may be based on datatypeBGDT:PartyRoleCode. RoleCategoryCode may have a multiplicity of 1 andmay be based on datatype BGDT:PartyRoleCategoryCode. MainIndicator mayhave a multiplicity of 0 . . . 1 and may be based on datatypeCDT:Indicator. Party includes the following node elements: ContactParty,in a 1:CN cardinality relationship.

The package OpportunityPartyContactParty includes the entityContactParty. ContactParty includes the following non-node elements:PartyID, RoleCode, RecipientPartyID, and MainIndicator. PartyID may havea multiplicity of 0 . . . 1 and may be based on datatype BGDT:PartyID.RoleCode may have a multiplicity of 0 . . . 1 and may be based ondatatype BGDT:PartyRoleCode. RecipientPartyID may have a multiplicity of0 . . . 1 and may be based on datatype BGDT:PartyID. MainIndicator mayhave a multiplicity of 0 . . . 1 and may be based on datatypeCDT:Indicator.

The package OpportunitySalesCycle includes the entity SalesCycle.SalesCycle includes the following non-node elements: SalesCycleCode,SalesCyclePhaseCode, and PhaseProcessingPeriod. SalesCycleCode may havea multiplicity of 0 . . . 1 and may be based on datatypeBGDT:SalesCycleCode. SalesCyclePhaseCode may have a multiplicity of 0 .. . 1 and may be based on datatype BGDT:SalesCyclePhaseCode.PhaseProcessingPeriod may have a multiplicity of 0 . . . 1 and may bebased on datatype AGDT:DatePeriod.

The package OpportunitySalesForecast includes the entity SalesForecast.SalesForecast includes the following non-node elements:ProbabilityPercent, ExpectedRevenueAmount,SalesRevenueForecastRelevanceIndicator, WeightedExpectedNetAmount,ProspectBudgetAmount, and ExpectedProcessingDatePeriod.ProbabilityPercent may have a multiplicity of 0 . . . 1 and may be basedon datatype CDT:Percent. ExpectedRevenueAmount may have a multiplicityof 0 . . . 1 and may be based on datatype CDT:Amount.SalesRevenueForecastRelevanceIndicator may have a multiplicity of 0 . .. 1 and may be based on datatype CDT:Indicator.WeightedExpectedNetAmount may have a multiplicity of 0 . . . 1 and maybe based on datatype CDT:Amount. ProspectBudgetAmount may have amultiplicity of 0 . . . 1 and may be based on datatype CDT:Amount.ExpectedProcessingDatePeriod may have a multiplicity of 0 . . . 1 andmay be based on datatype AGDT:CLOSED_DatePeriod.

The package OpportunitySalesAndServiceBusinessArea includes the entitySalesAndServiceBusinessArea. SalesAndServiceBusinessArea includes thefollowing non-node elements: SalesOrganisationID,RecipientSalesOrganisationID, and DistributionChannelCode.SalesOrganisationID may have a multiplicity of 0 . . . 1 and may bebased on datatype BGDT:OrganisationalCentreID.RecipientSalesOrganisationID may have a multiplicity of 0 . . . 1 andmay be based on datatype BGDT:OrganisationalCentreID.DistributionChannelCode may have a multiplicity of 0 . . . 1 and may bebased on datatype BGDT:DistributionChannelCode.

The package OpportunityBusinessTransactionDocumentReference includes theentity BusinessTransactionDocumentReference.BusinessTransactionDocumentReference includes the following non-nodeelements: BusinessTransactionDocumentReference andBusinessTransactionDocumentRelationshipRoleCode.BusinessTransactionDocumentReference may have a multiplicity of 0 . . .1 and may be based on datatypeAGDT:BusinessTransactionDocumentReference.BusinessTransactionDocumentRelationshipRoleCode may have a multiplicityof 0 . . . 1 and may be based on datatypeBGDT:BusinessTransactionDocumentRelationshipRoleCode.

The package OpportunityAttachmentFolder includes the sub-packageDocument and the entity AttachmentFolder. AttachmentFolder is typed bydatatype AttachmentFolder. The package OpportunityTextCollectionincludes the sub-package Text and the entity TextCollection.TextCollection includes the following node elements: Text, in a 1:Ncardinality relationship.

The package OpportunityTextCollectionText includes the entity Text. Textincludes the TypeCode non-node element, which may have a multiplicity of1 and may be based on datatype BGDT:TextCollectionTextTypeCode. Textincludes the following node elements: ContentText, in a 1:1 cardinalityrelationship. ContentText is typed by datatype Text.

The package OpportunityItem includes the sub-packagesBusinessTransactionDocumentReference and ItemProduct and the entityItem. Item includes the following non-node elements: ID,ProcessingTypeCode, Description, Quantity, and ExpectedNetAmount. ID mayhave a multiplicity of 1 and may be based on datatypeBGDT:BusinessTransactionDocumentItemIDProcessingTypeCode may have amultiplicity of 0 . . . 1 and may be based on datatypeBGDT:BusinessTransactionDocumentItemProcessingTypeCode. Description mayhave a multiplicity of 0 . . . 1 and may be based on datatypeBGDT:SHORT_Description. Quantity may have a multiplicity of 0 . . . 1and may be based on datatype CDT:Quantity. ExpectedNetAmount may have amultiplicity of 0 . . . 1 and may be based on datatype CDT:Amount. Itemincludes the following node elements:BusinessTransactionDocumentReference, in a 1:CN cardinalityrelationship; and ItemProduct, in a 1:C cardinality relationship.

The package OpportunityItemBusinessTransactionDocumentReference includesthe entity BusinessTransactionDocumentReference.BusinessTransactionDocumentReference includes the following non-nodeelements: BusinessTransactionDocumentReference andBusinessTransactionDocumentRelationshipRoleCode.BusinessTransactionDocumentReference may have a multiplicity of 0 . . .1 and may be based on datatypeAGDT:BusinessTransactionDocumentReference.BusinessTransactionDocumentRelationshipRoleCode may have a multiplicityof 0 . . . 1 and may be based on datatypeBGDT:BusinessTransactionDocumentRelationshipRoleCode.

The package OpportunityItemItemProduct includes the entity ItemProduct.ItemProduct includes the following non-node elements: ProductID,RecipientProductID, ProductTypeCode, ProductCategoryHierarchyID,RecipientProductCategoryHierarchyID, ProductCategoryInternalID, andRecipientProductCategoryInternalID. ProductID may have a multiplicity of0 . . . 1 and may be based on datatype BGDT:ProductID.RecipientProductID may have a multiplicity of 0 . . . 1 and may be basedon datatype BGDT:ProductID. ProductTypeCode may have a multiplicity of 0. . . 1 and may be based on datatype BGDT:ProductTypeCode.ProductCategoryHierarchyID may have a multiplicity of 0 . . . 1 and maybe based on datatype BGDT:ProductCategoryHierarchyID.RecipientProductCategoryHierarchyID may have a multiplicity of 0 . . . 1and may be based on datatype BGDT:ProductCategoryHierarchyID.ProductCategoryInternalID may have a multiplicity of 0 . . . 1 and maybe based on datatype BGDT:ProductCategoryInternalID.RecipientProductCategoryInternalID may have a multiplicity of 0 . . . 1and may be based on datatype BGDT:ProductCategoryInternalID.

FIG. 33 illustrates one example logical configuration of an OpportunityReplication Confirmation message 33000. Specifically, this figuredepicts the arrangement and hierarchy of various components such as oneor more levels of packages, entities, and data types, shown here as33002 through 33012. As described above, packages may be used torepresent hierarchy levels, and different types of cardinalityrelationships among entities can be represented using differentarrowhead styles. Entities are discrete business elements that are usedduring a business transaction. Data types are used to type objectentities and interfaces with a structure. For example, the OpportunityReplication Confirmation message 33000 includes, among other things, theOpportunity entity 33006. Accordingly, heterogeneous applications maycommunicate using this consistent message configured as such.

The message type Opportunity Replication Confirmation is derived fromthe business object Opportunity as a leading object together with itsoperation signature. The message type Opportunity ReplicationConfirmation is a confirmation of replicated opportunity data. Thestructure of the message type Opportunity Replication Confirmation isdetermined by the message data typeOpportunityReplicationConfirmationMessage. The message data typeOpportunityReplicationConfirmationMessage includes the MessageHeaderpackage and the Opportunity package. The package MessageHeader includesthe sub-packages Party and Business Scope and the entity MessageHeader.MessageHeader is a grouping of business information from a perspectiveof a sending application, including information to identify a businessdocument in a message, information about a sender, and information abouta recipient, which may be optional. MessageHeader is typed by datatypeBusinessDocumentMessageHeader.

The package Opportunity includes the sub-packagesBusinessTransactionDocumentReference and Item and the entityOpportunity. Opportunity includes the ID non-node element, which mayhave a multiplicity of 1 and may be based on datatypeBGDT:BusinessTransactionDocumentID. Opportunity includes the followingnode elements: OpportunityReference, in a 1:C cardinality relationship;and Item, in a 1:CN cardinality relationship.

The package OpportunityBusinessTransactionDocumentReference includes theentity OpportunityReference. OpportunityReference is typed by datatypeBusinessTransactionDocumentReference.

The package OpportunityItem includes the sub-packageItemBusinessTransactionDocumentReference and the entity Item. Itemincludes the ID non-node element, which may have a multiplicity of 1 andmay be based on datatype BGDT:BusinessTransactionDocumentItemID Itemincludes the following node elements: OpportunityItemReference, in a 1:Ccardinality relationship.

The package OpportunityItemItemBusinessTransactionDocumentReferenceincludes the entity OpportunityItemReference. OpportunityItemReferenceis typed by datatype BusinessTransactionDocumentReference.

FIGS. 34-1 through 34-19 show an example configuration of an ElementStructure that includes an OpportunityReplicationRequest 34000 package.Specifically, these figures depict the arrangement and hierarchy ofvarious components such as one or more levels of packages, entities, anddatatypes, shown here as 34000 through 34592. As described above,packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example, the OpportunityReplicationRequest 34000includes, among other things, an OpportunityReplicationRequest 34002.Accordingly, heterogeneous applications may communicate using thisconsistent message configured as such.

The OpportunityReplicationRequest 34000 package is anOpportunityReplicationRequest 34004 data type. TheOpportunityReplicationRequest 34000 package includes anOpportunityReplicationRequest 34002 entity. TheOpportunityReplicationRequest 34000 package includes various packages,namely a MessageHeader 34006 and an Opportunity 34014.

The MessageHeader 34006 package is a BusinessDocumentMessageHeader 34012data type. The MessageHeader 34006 package includes a MessageHeader34008 entity. The MessageHeader 34008 entity has a cardinality of 134010 meaning that for each instance of the MessageHeader 34006 packagethere is one MessageHeader 34008 entity.

The Opportunity 34014 package is an OpportunityReplicationRequestRoot34020 data type. The Opportunity 34014 package includes an Opportunity34016 entity. The Opportunity 34014 package includes various packages,namely a Status 34082, a ProspectParty 34096, a CompetitorParty 34154, aSalesEmployeeParty 34186, an EmployeeResponsible 34212, a SalesUnitParty34238, a Party 34264, a SalesCycle 34334, a SalesForecast 34360, aSalesAndServiceBusinessArea 34404, aBusinessTransactionDocumentReference 34430, an AttachmentFolder 34450, aTextCollection 34458 and an Item 34486.

The Opportunity 34016 entity has a cardinality of 1 34018 meaning thatfor each instance of the Opportunity 34014 package there is oneOpportunity 34016 entity. The Opportunity 34016 entity includes variousattributes, namely an ID 34022, a SystemAdministrativeData 34028, aProcessingTypeCode 34034, a Name 34040, a PriorityCode 34046, aProcessStatusValidSinceDate 34052, a GroupCode 34058, an OriginTypeCode34064, a ResultReasonCode 34070 and a ChangeOrdinalNumberValue 34076.

The ID 34022 attribute is a BusinessTransactionDocumentID 34026 datatype. The ID 34022 attribute has a cardinality of 1 34024 meaning thatfor each instance of the Opportunity 34016 entity there is one ID 34022attribute. The SystemAdministrativeData 34028 attribute is anUSERACCOUNTBASED_SystemAdministrativeData 34032 data type. TheSystemAdministrativeData 34028 attribute has a cardinality of 0 . . . 134030 meaning that for each instance of the Opportunity 34016 entitythere may be one SystemAdministrativeData 34028 attribute.

The ProcessingTypeCode 34034 attribute is aBusinessTransactionDocumentProcessingTypeCode 34038 data type. TheProcessingTypeCode 34034 attribute has a cardinality of 1 34036 meaningthat for each instance of the Opportunity 34016 entity there is oneProcessingTypeCode 34034 attribute. The Name 34040 attribute is anEXTENDED_Name 34044 data type. The Name 34040 attribute has acardinality of 0 . . . 1 34042 meaning that for each instance of theOpportunity 34016 entity there may be one Name 34040 attribute.

The PriorityCode 34046 attribute is a PriorityCode 34050 data type. ThePriorityCode 34046 attribute has a cardinality of 0 . . . 1 34048meaning that for each instance of the Opportunity 34016 entity there maybe one PriorityCode 34046 attribute. The ProcessStatusValidSinceDate34052 attribute is a Date 34056 data type. TheProcessStatusValidSinceDate 34052 attribute has a cardinality of 1 34054meaning that for each instance of the Opportunity 34016 entity there isone ProcessStatusValidSinceDate 34052 attribute.

The GroupCode 34058 attribute is an OpportunityGroupCode 34062 datatype. The GroupCode 34058 attribute has a cardinality of 0 . . . 1 34060meaning that for each instance of the Opportunity 34016 entity there maybe one GroupCode 34058 attribute. The OriginTypeCode 34064 attribute isa CustomerTransactionDocumentOriginTypeCode 34068 data type. TheOriginTypeCode 34064 attribute has a cardinality of 0 . . . 1 34066meaning that for each instance of the Opportunity 34016 entity there maybe one OriginTypeCode 34064 attribute.

The ResultReasonCode 34070 attribute is aCustomerTransactionDocumentResultReasonCode 34074 data type. TheResultReasonCode 34070 attribute has a cardinality of 0 . . . 1 34072meaning that for each instance of the Opportunity 34016 entity there maybe one ResultReasonCode 34070 attribute. The ChangeOrdinalNumberValue34076 attribute is an OrdinalNumberValueV1 34080 data type. TheChangeOrdinalNumberValue 34076 attribute has a cardinality of 0 . . . 134078 meaning that for each instance of the Opportunity 34016 entitythere may be one ChangeOrdinalNumberValue 34076 attribute.

The Status 34082 package is an OpportunityReplicationOpportunityStatus34088 data type. The Status 34082 package includes a Status 34084entity. The Status 34084 entity has a cardinality of 1 34086 meaningthat for each instance of the Status 34082 package there is one Status34084 entity. The Status 34084 entity includes a LifeCycleStatusCode34090 attribute.

The LifeCycleStatusCode 34090 attribute is anOpportunityLifeCycleStatusCode 34094 data type. The LifeCycleStatusCode34090 attribute has a cardinality of 0 . . . 1 34092 meaning that foreach instance of the Status 34084 entity there may be oneLifeCycleStatusCode 34090 attribute.

The ProspectParty 34096 package is anOpportunityReplicationProspectParty 34102 data type. The ProspectParty34096 package includes a ProspectParty 34098 entity. The ProspectParty34096 package includes a ContactParty 34122 package. The ProspectParty34098 entity has a cardinality of 0 . . . 1 34100 meaning that for eachinstance of the ProspectParty 34096 package there may be oneProspectParty 34098 entity. The ProspectParty 34098 entity includesvarious attributes, namely a PartyID 34104, a RecipientPartyID 34110 anda RoleCode 34116.

The PartyID 34104 attribute is a PartyID 34108 data type. The PartyID34104 attribute has a cardinality of 1 34106 meaning that for eachinstance of the ProspectParty 34098 entity there is one PartyID 34104attribute. The RecipientPartyID 34110 attribute is a PartyID 34114 datatype. The RecipientPartyID 34110 attribute has a cardinality of 0 . . .1 34112 meaning that for each instance of the ProspectParty 34098 entitythere may be one RecipientPartyID 34110 attribute. The RoleCode 34116attribute is a PartyRoleCode 34120 data type. The RoleCode 34116attribute has a cardinality of 0 . . . 1 34118 meaning that for eachinstance of the ProspectParty 34098 entity there may be one RoleCode34116 attribute.

The ContactParty 34122 package is anOpportunityReplicationPartyWithMainIndicator 34128 data type. TheContactParty 34122 package includes a ContactParty 34124 entity. TheContactParty 34124 entity has a cardinality of 0 . . . N 34126 meaningthat for each instance of the ContactParty 34122 package there may beone or more ContactParty 34124 entities. The ContactParty 34124 entityincludes various attributes, namely a PartyID 34130, a RoleCode 34136, aRecipientPartyID 34142 and a MainIndicator 34148.

The PartyID 34130 attribute is a PartyID 34134 data type. The PartyID34130 attribute has a cardinality of 0 . . . 1 34132 meaning that foreach instance of the ContactParty 34124 entity there may be one PartyID34130 attribute. The RoleCode 34136 attribute is a PartyRoleCode 34140data type. The RoleCode 34136 attribute has a cardinality of 0 . . . 134138 meaning that for each instance of the ContactParty 34124 entitythere may be one RoleCode 34136 attribute.

The RecipientPartyID 34142 attribute is a PartyID 34146 data type. TheRecipientPartyID 34142 attribute has a cardinality of 0 . . . 1 34144meaning that for each instance of the ContactParty 34124 entity theremay be one RecipientPartyID 34142 attribute. The MainIndicator 34148attribute is an Indicator 34152 data type. The MainIndicator 34148attribute has a cardinality of 0 . . . 1 34150 meaning that for eachinstance of the ContactParty 34124 entity there may be one MainIndicator34148 attribute.

The CompetitorParty 34154 package is anOpportunityReplicationPartyWithMainIndicator 34160 data type. TheCompetitorParty 34154 package includes a CompetitorParty 34156 entity.The CompetitorParty 34156 entity has a cardinality of 0 . . . N 34158meaning that for each instance of the CompetitorParty 34154 packagethere may be one or more CompetitorParty 34156 entities. TheCompetitorParty 34156 entity includes various attributes, namely aPartyID 34162, a RoleCode 34168, a RecipientPartyID 34174 and aMainIndicator 34180.

The PartyID 34162 attribute is a PartyID 34166 data type. The PartyID34162 attribute has a cardinality of 0 . . . 1 34164 meaning that foreach instance of the CompetitorParty 34156 entity there may be onePartyID 34162 attribute. The RoleCode 34168 attribute is a PartyRoleCode34172 data type. The RoleCode 34168 attribute has a cardinality of 0 . .. 1 34170 meaning that for each instance of the CompetitorParty 34156entity there may be one RoleCode 34168 attribute.

The RecipientPartyID 34174 attribute is a PartyID 34178 data type. TheRecipientPartyID 34174 attribute has a cardinality of 0 . . . 1 34176meaning that for each instance of the CompetitorParty 34156 entity theremay be one RecipientPartyID 34174 attribute. The MainIndicator 34180attribute is an Indicator 34184 data type. The MainIndicator 34180attribute has a cardinality of 0 . . . 1 34182 meaning that for eachinstance of the CompetitorParty 34156 entity there may be oneMainIndicator 34180 attribute.

The SalesEmployeeParty 34186 package is anOpportunityReplicationPartyWithOutMainIndicator 34192 data type. TheSalesEmployeeParty 34186 package includes a SalesEmployeeParty 34188entity. The SalesEmployeeParty 34188 entity has a cardinality of 0 . . .N 34190 meaning that for each instance of the SalesEmployeeParty 34186package there may be one or more SalesEmployeeParty 34188 entities. TheSalesEmployeeParty 34188 entity includes various attributes, namely aPartyID 34194, a RecipientPartyID 34200 and a RoleCode 34206.

The PartyID 34194 attribute is a PartyID 34198 data type. The PartyID34194 attribute has a cardinality of 0 . . . 1 34196 meaning that foreach instance of the SalesEmployeeParty 34188 entity there may be onePartyID 34194 attribute. The RecipientPartyID 34200 attribute is aPartyID 34204 data type. The RecipientPartyID 34200 attribute has acardinality of 0 . . . 1 34202 meaning that for each instance of theSalesEmployeeParty 34188 entity there may be one RecipientPartyID 34200attribute. The RoleCode 34206 attribute is a PartyRoleCode 34210 datatype. The RoleCode 34206 attribute has a cardinality of 0 . . . 1 34208meaning that for each instance of the SalesEmployeeParty 34188 entitythere may be one RoleCode 34206 attribute.

The EmployeeResponsible 34212 package is anOpportunityReplicationPartyWithOutMainIndicator 34218 data type. TheEmployeeResponsible 34212 package includes an EmployeeResponsible 34214entity. The EmployeeResponsible 34214 entity has a cardinality of 0 . .. 1 34216 meaning that for each instance of the EmployeeResponsible34212 package there may be one EmployeeResponsible 34214 entity. TheEmployeeResponsible 34214 entity includes various attributes, namely aPartyID 34220, a RecipientPartyID 34226 and a RoleCode 34232.

The PartyID 34220 attribute is a PartyID 34224 data type. The PartyID34220 attribute has a cardinality of 0 . . . 1 34222 meaning that foreach instance of the EmployeeResponsible 34214 entity there may be onePartyID 34220 attribute. The RecipientPartyID 34226 attribute is aPartyID 34230 data type. The RecipientPartyID 34226 attribute has acardinality of 0 . . . 1 34228 meaning that for each instance of theEmployeeResponsible 34214 entity there may be one RecipientPartyID 34226attribute. The RoleCode 34232 attribute is a PartyRoleCode 34236 datatype. The RoleCode 34232 attribute has a cardinality of 0 . . . 1 34234meaning that for each instance of the EmployeeResponsible 34214 entitythere may be one RoleCode 34232 attribute.

The SalesUnitParty 34238 package is anOpportunityReplicationPartyWithOutMainIndicator 34244 data type. TheSalesUnitParty 34238 package includes a SalesUnitParty 34240 entity. TheSalesUnitParty 34240 entity has a cardinality of 0 . . . 1 34242 meaningthat for each instance of the SalesUnitParty 34238 package there may beone SalesUnitParty 34240 entity. The SalesUnitParty 34240 entityincludes various attributes, namely a PartyID 34246, a RecipientPartyID34252 and a RoleCode 34258.

The PartyID 34246 attribute is a PartyID 34250 data type. The PartyID34246 attribute has a cardinality of 0 . . . 1 34248 meaning that foreach instance of the SalesUnitParty 34240 entity there may be onePartyID 34246 attribute. The RecipientPartyID 34252 attribute is aPartyID 34256 data type. The RecipientPartyID 34252 attribute has acardinality of 0 . . . 1 34254 meaning that for each instance of theSalesUnitParty 34240 entity there may be one RecipientPartyID 34252attribute. The RoleCode 34258 attribute is a PartyRoleCode 34262 datatype. The RoleCode 34258 attribute has a cardinality of 0 . . . 1 34260meaning that for each instance of the SalesUnitParty 34240 entity theremay be one RoleCode 34258 attribute.

The Party 34264 package is an OpportunityReplicationParty 34270 datatype. The Party 34264 package includes a Party 34266 entity. The Party34264 package includes a ContactParty 34302 package. The Party 34266entity has a cardinality of 0 . . . N 34268 meaning that for eachinstance of the Party 34264 package there may be one or more Party 34266entities. The Party 34266 entity includes various attributes, namely aPartyID 34272, a RecipientPartyID 34278, a RoleCode 34284, aRoleCategoryCode 34290 and a MainIndicator 34296.

The PartyID 34272 attribute is a PartyID 34276 data type. The PartyID34272 attribute has a cardinality of 1 34274 meaning that for eachinstance of the Party 34266 entity there is one PartyID 34272 attribute.The RecipientPartyID 34278 attribute is a PartyID 34282 data type. TheRecipientPartyID 34278 attribute has a cardinality of 0 . . . 1 34280meaning that for each instance of the Party 34266 entity there may beone RecipientPartyID 34278 attribute.

The RoleCode 34284 attribute is a PartyRoleCode 34288 data type. TheRoleCode 34284 attribute has a cardinality of 0 . . . 1 34286 meaningthat for each instance of the Party 34266 entity there may be oneRoleCode 34284 attribute. The RoleCategoryCode 34290 attribute is aPartyRoleCategoryCode 34294 data type. The RoleCategoryCode 34290attribute has a cardinality of 1 34292 meaning that for each instance ofthe Party 34266 entity there is one RoleCategoryCode 34290 attribute.The MainIndicator 34296 attribute is an Indicator 34300 data type. TheMainIndicator 34296 attribute has a cardinality of 0 . . . 1 34298meaning that for each instance of the Party 34266 entity there may beone MainIndicator 34296 attribute.

The ContactParty 34302 package is anOpportunityReplicationPartyWithMainIndicator 34308 data type. TheContactParty 34302 package includes a ContactParty 34304 entity. TheContactParty 34304 entity has a cardinality of 0 . . . N 34306 meaningthat for each instance of the ContactParty 34302 package there may beone or more ContactParty 34304 entities. The ContactParty 34304 entityincludes various attributes, namely a PartyID 34310, a RoleCode 34316, aRecipientPartyID 34322 and a MainIndicator 34328.

The PartyID 34310 attribute is a PartyID 34314 data type. The PartyID34310 attribute has a cardinality of 0 . . . 1 34312 meaning that foreach instance of the ContactParty 34304 entity there may be one PartyID34310 attribute. The RoleCode 34316 attribute is a PartyRoleCode 34320data type. The RoleCode 34316 attribute has a cardinality of 0 . . . 134318 meaning that for each instance of the ContactParty 34304 entitythere may be one RoleCode 34316 attribute.

The RecipientPartyID 34322 attribute is a PartyID 34326 data type. TheRecipientPartyID 34322 attribute has a cardinality of 0 . . . 1 34324meaning that for each instance of the ContactParty 34304 entity theremay be one RecipientPartyID 34322 attribute. The MainIndicator 34328attribute is an Indicator 34332 data type. The MainIndicator 34328attribute has a cardinality of 0 . . . 1 34330 meaning that for eachinstance of the ContactParty 34304 entity there may be one MainIndicator34328 attribute.

The SalesCycle 34334 package is an OpportunityReplicationSalesCycle34340 data type. The SalesCycle 34334 package includes a SalesCycle34336 entity. The SalesCycle 34336 entity has a cardinality of 0 . . . 134338 meaning that for each instance of the SalesCycle 34334 packagethere may be one SalesCycle 34336 entity. The SalesCycle 34336 entityincludes various attributes, namely a SalesCycleCode 34342, aSalesCyclePhaseCode 34348 and a PhaseProcessingPeriod 34354.

The SalesCycleCode 34342 attribute is a SalesCycleCode 34346 data type.The SalesCycleCode 34342 attribute has a cardinality of 0 . . . 1 34344meaning that for each instance of the SalesCycle 34336 entity there maybe one SalesCycleCode 34342 attribute. The SalesCyclePhaseCode 34348attribute is a SalesCyclePhaseCode 34352 data type. TheSalesCyclePhaseCode 34348 attribute has a cardinality of 0 . . . 1 34350meaning that for each instance of the SalesCycle 34336 entity there maybe one SalesCyclePhaseCode 34348 attribute. The PhaseProcessingPeriod34354 attribute is a DatePeriod 34358 data type. ThePhaseProcessingPeriod 34354 attribute has a cardinality of 0 . . . 134356 meaning that for each instance of the SalesCycle 34336 entitythere may be one PhaseProcessingPeriod 34354 attribute.

The SalesForecast 34360 package is anOpportunityReplicationSalesForecast 34366 data type. The SalesForecast34360 package includes a SalesForecast 34362 entity. The SalesForecast34362 entity has a cardinality of 0 . . . 1 34364 meaning that for eachinstance of the SalesForecast 34360 package there may be oneSalesForecast 34362 entity. The SalesForecast 34362 entity includesvarious attributes, namely a ProbabilityPercent 34368, anExpectedRevenueAmount 34374, a SalesRevenueForecastRelevanceIndicator34380, a WeightedExpectedNetAmount 34386, a ProspectBudgetAmount 34392and an ExpectedProcessingDatePeriod 34398.

The ProbabilityPercent 34368 attribute is a Percent 34372 data type. TheProbabilityPercent 34368 attribute has a cardinality of 0 . . . 1 34370meaning that for each instance of the SalesForecast 34362 entity theremay be one ProbabilityPercent 34368 attribute. The ExpectedRevenueAmount34374 attribute is an Amount 34378 data type. The ExpectedRevenueAmount34374 attribute has a cardinality of 0 . . . 1 34376 meaning that foreach instance of the SalesForecast 34362 entity there may be oneExpectedRevenueAmount 34374 attribute.

The SalesRevenueForecastRelevanceIndicator 34380 attribute is anIndicator 34384 data type. The SalesRevenueForecastRelevanceIndicator34380 attribute has a cardinality of 0 . . . 1 34382 meaning that foreach instance of the SalesForecast 34362 entity there may be oneSalesRevenueForecastRelevanceIndicator 34380 attribute. TheWeightedExpectedNetAmount 34386 attribute is an Amount 34390 data type.The WeightedExpectedNetAmount 34386 attribute has a cardinality of 0 . .. 1 34388 meaning that for each instance of the SalesForecast 34362entity there may be one WeightedExpectedNetAmount 34386 attribute.

The ProspectBudgetAmount 34392 attribute is an Amount 34396 data type.The ProspectBudgetAmount 34392 attribute has a cardinality of 0 . . . 134394 meaning that for each instance of the SalesForecast 34362 entitythere may be one ProspectBudgetAmount 34392 attribute. TheExpectedProcessingDatePeriod 34398 attribute is a CLOSED_DatePeriod34402 data type. The ExpectedProcessingDatePeriod 34398 attribute has acardinality of 0 . . . 1 34400 meaning that for each instance of theSalesForecast 34362 entity there may be one ExpectedProcessingDatePeriod34398 attribute.

The SalesAndServiceBusinessArea 34404 package is anOpportunityReplicationSalesBusinessArea 34410 data type. TheSalesAndServiceBusinessArea 34404 package includes aSalesAndServiceBusinessArea 34406 entity. TheSalesAndServiceBusinessArea 34406 entity has a cardinality of 0 . . . 134408 meaning that for each instance of the SalesAndServiceBusinessArea34404 package there may be one SalesAndServiceBusinessArea 34406 entity.The SalesAndServiceBusinessArea 34406 entity includes variousattributes, namely a SalesOrganisationID 34412, aRecipientSalesOrganisationID 34418 and a DistributionChannelCode 34424.

The SalesOrganisationID 34412 attribute is an OrganisationalCentreID34416 data type. The SalesOrganisationID 34412 attribute has acardinality of 0 . . . 1 34414 meaning that for each instance of theSalesAndServiceBusinessArea 34406 entity there may be one SalesOrganisationID 34412 attribute. The RecipientSalesOrganisationID 34418attribute is an OrganisationalCentreID 34422 data type. TheRecipientSalesOrganisationID 34418 attribute has a cardinality of 0 . .. 1 34420 meaning that for each instance of theSalesAndServiceBusinessArea 34406 entity there may be oneRecipientSalesOrganisationID 34418 attribute. TheDistributionChannelCode 34424 attribute is a DistributionChannelCode34428 data type. The DistributionChannelCode 34424 attribute has acardinality of 0 . . . 1 34426 meaning that for each instance of theSalesAndServiceBusinessArea 34406 entity there may be oneDistributionChannelCode 34424 attribute.

The BusinessTransactionDocumentReference 34430 package is anOpportunityReplicationBusinessTransactionDocumentReference 34436 datatype. The BusinessTransactionDocumentReference 34430 package includes aBusinessTransactionDocumentReference 34432 entity. TheBusinessTransactionDocumentReference 34432 entity has a cardinality of 0. . . N 34434 meaning that for each instance of theBusinessTransactionDocumentReference 34430 package there may be one ormore BusinessTransactionDocumentReference 34432 entities. TheBusinessTransactionDocumentReference 34432 entity includes variousattributes, namely a BusinessTransactionDocumentReference 34438 and aBusinessTransactionDocumentRelationshipRoleCode 34444.

The BusinessTransactionDocumentReference 34438 attribute is aBusinessTransactionDocumentReference 34442 data type. TheBusinessTransactionDocumentReference 34438 attribute has a cardinalityof 0 . . . 1 34440 meaning that for each instance of theBusinessTransactionDocumentReference 34432 entity there may be oneBusinessTransactionDocumentReference 34438 attribute. TheBusinessTransactionDocumentRelationshipRoleCode 34444 attribute is aBusinessTransactionDocumentRelationshipRoleCode 34448 data type. TheBusinessTransactionDocumentRelationshipRoleCode 34444 attribute has acardinality of 0 . . . 1 34446 meaning that for each instance of theBusinessTransactionDocumentReference 34432 entity there may be oneBusinessTransactionDocumentRelationshipRoleCode 34444 attribute.

The AttachmentFolder 34450 package is an AttachmentFolder 34456 datatype. The AttachmentFolder 34450 package includes an AttachmentFolder34452 entity. The AttachmentFolder 34452 entity has a cardinality of 0 .. . 1 34454 meaning that for each instance of the AttachmentFolder 34450package there may be one AttachmentFolder 34452 entity.

The TextCollection 34458 package is a TextCollection 34464 data type.The TextCollection 34458 package includes a TextCollection 34460 entity.The TextCollection 34458 package includes a Text 34466 package. TheTextCollection 34460 entity has a cardinality of 0 . . . 1 34462 meaningthat for each instance of the TextCollection 34458 package there may beone TextCollection 34460 entity.

The Text 34466 package is a Text 34472 data type. The Text 34466 packageincludes a Text 34468 entity. The Text 34468 entity has a cardinality of1 . . . N 34470 meaning that for each instance of the Text 34466 packagethere are one or more Text 34468 entities. The Text 34468 entityincludes various attributes, namely a TypeCode 34474 and a ContentText34480.

The TypeCode 34474 attribute is a TextCollectionTextTypeCode 34478 datatype. The TypeCode 34474 attribute has a cardinality of 1 34476 meaningthat for each instance of the Text 34468 entity there is one TypeCode34474 attribute. The ContentText 34480 attribute is a Text 34484 datatype. The ContentText 34480 attribute has a cardinality of 1 34482meaning that for each instance of the Text 34468 entity there is oneContentText 34480 attribute.

The Item 34486 package is an OpportunityReplicationhem 34492 data type.The Item 34486 package includes an Item 34488 entity. The Item 34486package includes various packages, namely aBusinessTransactionDocumentReference 34524 and an ItemProduct 34544. TheItem 34488 entity has a cardinality of 0 . . . N 34490 meaning that foreach instance of the Item 34486 package there may be one or more Item34488 entities. The Item 34488 entity includes various attributes,namely an ID 34494, a ProcessingTypeCode 34500, a Description 34506, aQuantity 34512 and an ExpectedNetAmount 34518.

The ID 34494 attribute is a BusinessTransactionDocumentItemID 34498 datatype. The ID 34494 attribute has a cardinality of 1 34496 meaning thatfor each instance of the Item 34488 entity there is one ID 34494attribute. The ProcessingTypeCode 34500 attribute is aBusinessTransactionDocumentItemProcessingTypeCode 34504 data type. TheProcessingTypeCode 34500 attribute has a cardinality of 0 . . . 1 34502meaning that for each instance of the Item 34488 entity there may be oneProcessingTypeCode 34500 attribute.

The Description 34506 attribute is a SHORT_Description 34510 data type.The Description 34506 attribute has a cardinality of 0 . . . 1 34508meaning that for each instance of the Item 34488 entity there may be oneDescription 34506 attribute. The Quantity 34512 attribute is a Quantity34516 data type. The Quantity 34512 attribute has a cardinality of 0 . .. 1 34514 meaning that for each instance of the Item 34488 entity theremay be one Quantity 34512 attribute. The ExpectedNetAmount 34518attribute is an Amount 34522 data type. The ExpectedNetAmount 34518attribute has a cardinality of 0 . . . 1 34520 meaning that for eachinstance of the Item 34488 entity there may be one ExpectedNetAmount34518 attribute.

The BusinessTransactionDocumentReference 34524 package is anItemBusinessTransactionDocumentReference 34530 data type. TheBusinessTransactionDocumentReference 34524 package includes aBusinessTransactionDocumentReference 34526 entity. TheBusinessTransactionDocumentReference 34526 entity has a cardinality of 0. . . N 34528 meaning that for each instance of theBusinessTransactionDocumentReference 34524 package there may be one ormore BusinessTransactionDocumentReference 34526 entities. TheBusinessTransactionDocumentReference 34526 entity includes variousattributes, namely a BusinessTransactionDocumentReference 34532 and aBusinessTransactionDocumentRelationshipRoleCode 34538.

The BusinessTransactionDocumentReference 34532 attribute is aBusinessTransactionDocumentReference 34536 data type. TheBusinessTransactionDocumentReference 34532 attribute has a cardinalityof 0 . . . 1 34534 meaning that for each instance of theBusinessTransactionDocumentReference 34526 entity there may be oneBusinessTransactionDocumentReference 34532 attribute. TheBusinessTransactionDocumentRelationshipRoleCode 34538 attribute is aBusinessTransactionDocumentRelationshipRoleCode 34542 data type. TheBusinessTransactionDocumentRelationshipRoleCode 34538 attribute has acardinality of 0 . . . 1 34540 meaning that for each instance of theBusinessTransactionDocumentReference 34526 entity there may be oneBusinessTransactionDocumentRelationshipRoleCode 34538 attribute.

The ItemProduct 34544 package is an OpportunityReplicationProduct 34550data type. The ItemProduct 34544 package includes an ItemProduct 34546entity. The ItemProduct 34546 entity has a cardinality of 0 . . . 134548 meaning that for each instance of the ItemProduct 34544 packagethere may be one ItemProduct 34546 entity. The ItemProduct 34546 entityincludes various attributes, namely a ProductID 34552, aRecipientProductID 34558, a ProductTypeCode 34564, aProductCategoryHierarchyID 34570, a RecipientProductCategoryHierarchyID34576, a ProductCategoryInternalID 34582 and aRecipientProductCategoryInternalID 34588.

The ProductID 34552 attribute is a ProductID 34556 data type. TheProductID 34552 attribute has a cardinality of 0 . . . 1 34554 meaningthat for each instance of the ItemProduct 34546 entity there may be oneProductID 34552 attribute. The RecipientProductID 34558 attribute is aProductID 34562 data type. The RecipientProductID 34558 attribute has acardinality of 0 . . . 1 34560 meaning that for each instance of theItemProduct 34546 entity there may be one RecipientProductID 34558attribute.

The ProductTypeCode 34564 attribute is a ProductTypeCode 34568 datatype. The ProductTypeCode 34564 attribute has a cardinality of 0 . . . 134566 meaning that for each instance of the ItemProduct 34546 entitythere may be one ProductTypeCode 34564 attribute. TheProductCategoryHierarchyID 34570 attribute is aProductCategoryHierarchyID 34574 data type. TheProductCategoryHierarchyID 34570 attribute has a cardinality of 0 . . .1 34572 meaning that for each instance of the ItemProduct 34546 entitythere may be one ProductCategoryHierarchyID 34570 attribute.

The RecipientProductCategoryHierarchyID 34576 attribute is aProductCategoryHierarchyID 34580 data type. TheRecipientProductCategoryHierarchyID 34576 attribute has a cardinality of0 . . . 1 34578 meaning that for each instance of the ItemProduct 34546entity there may be one RecipientProductCategoryHierarchyID 34576attribute. The ProductCategoryInternalID 34582 attribute is aProductCategoryInternalID 34586 data type. The ProductCategoryInternalID34582 attribute has a cardinality of 0 . . . 1 34584 meaning that foreach instance of the ItemProduct 34546 entity there may be oneProductCategoryInternalID 34582 attribute. TheRecipientProductCategoryInternalID 34588 attribute is aProductCategoryInternalID 34592 data type. TheRecipientProductCategoryInternalID 34588 attribute has a cardinality of0 . . . 1 34590 meaning that for each instance of the ItemProduct 34546entity there may be one RecipientProductCategoryInternalID 34588attribute.

FIGS. 35-1 through 35-2 show an example configuration of an ElementStructure that includes an OpportunityReplicationConfirmation 35000package. Specifically, these figures depict the arrangement andhierarchy of various components such as one or more levels of packages,entities, and datatypes, shown here as 35000 through 35056. As describedabove, packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example, the OpportunityReplicationConfirmation 35000includes, among other things, an OpportunityReplicationConfirmation35002. Accordingly, heterogeneous applications may communicate usingthis consistent message configured as such.

The OpportunityReplicationConfirmation 35000 package is anOpportunityReplicationConfirmationMessage 35004 data type. TheOpportunityReplicationConfirmation 35000 package includes anOpportunityReplicationConfirmation 35002 entity. TheOpportunityReplicationConfirmation 35000 package includes variouspackages, namely a MessageHeader 35006 and an Opportunity 35014.

The MessageHeader 35006 package is a BusinessDocumentMessageHeader 35012data type. The MessageHeader 35006 package includes a MessageHeader35008 entity. The MessageHeader 35008 entity has a cardinality of 135010 meaning that for each instance of the MessageHeader 35006 packagethere is one MessageHeader 35008 entity.

The Opportunity 35014 package is an OpportunityReplicationConfirmation35020 data type. The Opportunity 35014 package includes an Opportunity35016 entity. The Opportunity 35014 package includes various packages,namely a BusinessTransactionDocumentReference 35028 and an Item 35036.The Opportunity 35016 entity has a cardinality of 1 35018 meaning thatfor each instance of the Opportunity 35014 package there is oneOpportunity 35016 entity. The Opportunity 35016 entity includes an ID35022 attribute. The ID 35022 attribute is aBusinessTransactionDocumentID 35026 data type. The ID 35022 attributehas a cardinality of 1 35024 meaning that for each instance of theOpportunity 35016 entity there is one ID 35022 attribute.

The BusinessTransactionDocumentReference 35028 package is aBusinessTransactionDocumentReference 35034 data type. TheBusinessTransactionDocumentReference 35028 package includes anOpportunityReference 35030 entity. The OpportunityReference 35030 entityhas a cardinality of 0 . . . 1 35032 meaning that for each instance ofthe BusinessTransactionDocumentReference 35028 package there may be oneOpportunityReference 35030 entity.

The Item 35036 package is anOpportunityReplicationConfirmationOpportunityItem 35042 data type. TheItem 35036 package includes an Item 35038 entity. The Item 35036 packageincludes an ItemBusinessTransactionDocumentReference 35050 package. TheItem 35038 entity has a cardinality of 0 . . . N 35040 meaning that foreach instance of the Item 35036 package there may be one or more Item35038 entities. The Item 35038 entity includes an ID 35044 attribute.The ID 35044 attribute is a BusinessTransactionDocumentItemID 35048 datatype. The ID 35044 attribute has a cardinality of 1 35046 meaning thatfor each instance of the Item 35038 entity there is one ID 35044attribute.

The ItemBusinessTransactionDocumentReference 35050 package is aBusinessTransactionDocumentReference 35056 data type. TheItemBusinessTransactionDocumentReference 35050 package includes anOpportunityItemReference 35052 entity. The OpportunityItemReference35052 entity has a cardinality of 0 . . . 1 35054 meaning that for eachinstance of the ItemBusinessTransactionDocumentReference 35050 packagethere may be one OpportunityItemReference 35052 entity.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. Accordingly, otherimplementations are within the scope of the following claims.

What is claimed is:
 1. A computer readable medium including program codefor providing a message-based interface for exchanging opportunity data,the medium comprising: program code for receiving via a message-basedinterface exposing at least one service as defined in a service registryand from a heterogeneous application executing in an environment ofcomputer systems providing message-based services, a first message forrequesting replication of opportunity data, including businesstransaction information and identification of parties involved in aprospective business transaction, the first message including a messagepackage hierarchically organized as: an opportunity replication requestmessage entity; and an opportunity package including an opportunityentity, wherein the opportunity entity includes an identifier, aprocessing type code and a process status valid since date; and whereinthe opportunity entity includes a status entity from a status package;and program code for sending a second message to the heterogeneousapplication responsive to the first message.
 2. The computer readablemedium of claim 1, wherein the opportunity entity further includes atleast one of the following: a prospect party entity from a prospectparty package, at least one competitor party entity from a competitorparty package, at least one sales employee party entity from a salesemployee party package, an employee responsible entity from an employeeresponsible party, a sales unit party entity from a sales unit partypackage, at least one party entity from a party package, a sales cycleentity from a sales cycle package, a sales forecast entity from a salesforecast package, a sales and service business area entity from a salesand service business area package, at least one business transactiondocument reference entity from a business transaction document referencepackage, an attachment folder entity from an attachment folder package,a text collection entity from a text collection package, and at leastone item entity from an item package.
 3. The computer readable medium ofclaim 1, wherein the opportunity entity further includes at least one ofthe following: system administrative data, a name, a priority code, agroup code, an origin type code, a result reason code, and a changeordinal number value.
 4. A distributed system operating in a landscapeof computer systems providing message-based services defined in aservice registry, the system comprising: a graphical user interfacecomprising computer readable instructions, embedded on tangible media,for requesting replication of opportunity data, including businesstransaction information and identification of parties involved in aprospective business transaction, the instructions using a request; afirst memory storing a user interface controller for processing therequest and involving a message including a message packagehierarchically organized as: an opportunity replication request messageentity; and an opportunity package including an opportunity entity,wherein the opportunity entity includes an identifier, a processing typecode and a process status valid since date; and wherein the opportunityentity includes a status entity from a status package; and a secondmemory, remote from the graphical user interface, storing a plurality ofservice interfaces, wherein one of the service interfaces is operable toprocess the message via the service interface.
 5. The distributed systemof claim 4, wherein the first memory is remote from the graphical userinterface.
 6. The distributed system of claim 4, wherein the firstmemory is remote from the second memory.